Conflicts using export *

Andreas Rossberg rossberg at google.com
Fri Jun 14 00:48:01 PDT 2013


What about:

    // M.js
    export * from "foo";
    export * from "foo";

    // foo.js
    export var x = 1;

Or:

    // M.js
    export * from "foo";
    export * from "bar";

    // foo.js
    export * from "foobar";

    // bar.js
    export * from "foobar";

    // foobar.js
    export var x = 1;

I just want to make sure that using M.x in any of these cases is an
error likewise.

/Andreas



On 13 June 2013 23:41, Brendan Eich <brendan at mozilla.com> wrote:
> Kevin Smith wrote:
>>
>>
>>     Also, I misspoke earlier.  The error is only if you *use* M.x, for the
>>     same reason.
>>
>>
>> Ah - subtle but important point.
>
>
> Yes, super-important in a growing independently-owned modules setting. I.e.,
> reality.
>
> /be
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss


More information about the es-discuss mailing list