ModuleImport

Kevin Smith zenparsing at gmail.com
Tue Jun 24 16:53:32 PDT 2014


>
>
>>
> I don't agree that the changes to the semantics are large, if we're
> talking about simply allowing a single syntactic form for both named and
> default import and Ron's option (A) (where default and named exports can
> not co-exist... until ES7 at least).
>

But unless you want to rewrite the design, you cannot prevent a default
export and named exports from co-existing:

    function F() { }
    export { F as default };  // Named and default
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140624/53c770a9/attachment-0001.html>


More information about the es-discuss mailing list