- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 20 Jun 2013 16:26:18 -0700
- To: Rick Waldron <waldron.rick@gmail.com>
- Cc: Justin Novosad <junov@google.com>, WHATWG <whatwg@whatwg.org>
On Thu, Jun 20, 2013 at 3:32 PM, Rick Waldron <waldron.rick@gmail.com> wrote: > On Thu, Jun 20, 2013 at 1:23 PM, Tab Atkins Jr. <jackalmage@gmail.com> > wrote: >> There's really no consistency here anyway, and the >> "Interface.create()" idiom is pretty easy and nice. >> >> I wonder - perhaps we can call the function "new"? Dunno which name is >> better. > > Can I ask that you steer clear of that? There has been discussion of > possibly providing static .new() on built-ins that produce instances without > new operator. I dont know where that stands, but of course it wouldn't be > revisited until ES7. It would be nice if that wasn't DOA due to > web-breakage. I suspect it was those half-remembered discussions that tickled my brain and caused me to suggest it. No problem avoiding it - we can just use .create(). ~TJ
Received on Thursday, 20 June 2013 23:27:03 UTC