Rationale for dropping ModuleImport syntax?

Kevin Smith zenparsing at gmail.com
Mon Jun 9 09:36:41 PDT 2014

IIUC, the motivation for dropping the form is that it's confusing to have
this other syntactic option which uses a different (contextual) keyword.

Well, we already have this:

    import "./foo";

which you can use when you want to load+execute but not import anything.
 Is that going away?  If not, then it makes sense to just add a renaming

    import "./foo" as foo;

Does that help with the confusion?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140609/96830cdf/attachment.html>

More information about the es-discuss mailing list