Rationale for dropping ModuleImport syntax?

Kevin Smith zenparsing at gmail.com
Mon Jun 9 09:29:38 PDT 2014

> Chris, the number of exports is not relevant, and in fact, there is no way
> to export all members in one go, which aligns well with the proposal to
> remove the way to import an object with all members. check the consumers of
> the `uikit` module, and count how many of those exported methods are used
> in a single module. In fact, this repo is consistent with what we have been
> saying. If you look at
> https://github.com/toshok/pirouette/blob/master/bindings/objc.js, it uses
> `module objc_internal from '@objc_internal';`, then it uses 5 methods
> exported by that module, which should not be a pain to declare them
> explicit as imports.

True, but that analysis doesn't apply to the example that I and Erik have

In sum, there are valid use cases for importing a large number of things
from a module.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140609/5e376295/attachment.html>

More information about the es-discuss mailing list