Rationale for dropping ModuleImport syntax?
zenparsing at gmail.com
Tue Jun 10 05:06:48 PDT 2014
> Agreed. Which is why I predict module makers will, at the encouragement of
> module consumers, stick to default-export only, since it is more in line
> with existing practice.
FWIW, I predict the opposite, but I could be wrong. A really good thing
about the current design is that it allows both possible futures to
Let's stick to the status quo. If there are cosmetic tweaks that need to
be made to `ModuleImport`, then let's do that instead of reopening old
debates without bringing new information. Let's not forget that the
current design is the result of a hard-earned compromise (a year old, BTW).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss