Conflicts using export *

Sam Tobin-Hochstadt samth at ccs.neu.edu
Fri Jun 14 04:53:28 PDT 2013


On Fri, Jun 14, 2013 at 3:48 AM, Andreas Rossberg <rossberg at google.com> wrote:
> 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.

In principle, I think it's better to allow these cases (think macros),
but I don't have strong feelings about it, so I'm fine with
disallowing them.

> 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
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss


More information about the es-discuss mailing list