Conflicts using export *
claus.reinke at talk21.com
Fri Jun 14 06:02:05 PDT 2013
>> I am confused: I thought "import *" was removed because, in the
>> presence of dynamically configured loaders, it would leave tools
>> (and programmers) unable to infer the local scope without executing code.
>> Now we have the same issue back via "export *", just need a re-exporting
>> intermediate module?
> No, you don't. `import *` affects the names bound in a module.
> `export *` doesn't. You still can't import a name without listing it
> explicitly, meaning that it's always easy to determine the local
Ah, thanks. That makes sense.
More information about the es-discuss