ES Modules: suggestions for improvement

Russell Leggett russell.leggett at gmail.com
Fri Jul 27 07:14:49 PDT 2012


On Tue, Jul 24, 2012 at 5:11 PM, Brendan Eich <brendan at mozilla.org> wrote:

> Sam Tobin-Hochstadt wrote:
>
>> But I don't think we should ban people from
>> using `import *` because sometimes it's hard to reason about.
>>
>
> Just to focus on import *, here's where I am:
>
> I'm in favor of deferring (not to say cutting) import *, in order to get
> ES6 modules spec'ed and avoid protracted maybe-good/maybe-bad arguments.
>
> If someone prototyping or REPL'ing feels the pain, they should wail in
> agony. Enough wailing and we'll figure out something for their use case --
> but not on the critical path for ES6.


+1 I'm all for deferring on this. Its easy to add later, but you can't take
it back. I'm used to using import * with Java, but I think the pattern
matching should be concise enough, and I think it probably the right level
of explicitness.

- Russ

>
>
> /be
>
> ______________________________**_________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20120727/dc48d6f5/attachment.html>


More information about the es-discuss mailing list