On Tue, Jul 24, 2012 at 5:11 PM, Brendan Eich <[email protected]> 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 > [email protected] > https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss> >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
