ModuleImport

Calvin Metcalf calvin.metcalf at gmail.com
Tue Jun 24 17:47:40 PDT 2014


Side note: is that legal?  I assumed you wouldn't be able to do that due to
default being a reserved word.
On Jun 24, 2014 7:53 PM, "Kevin Smith" <zenparsing at gmail.com> wrote:

>
>>>
>> 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
>
>
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140624/c2330088/attachment.html>


More information about the es-discuss mailing list