Rationale for dropping ModuleImport syntax?

Kevin Smith zenparsing at gmail.com
Wed Jun 11 12:41:53 PDT 2014

> I would second that.  I have seen no desire for any static analysis beyond
> "this module depends on that module" and I've seen no desire for live bound
> imports.
I believe that viewpoint is adequately represented in the status quo.  No
need to legislate other viewpoints away.

> I accept that we're messing with a fragile consensus, but the removal of
> ModuleImport syntax has already done that, so we're way beyond purely
> cosmetic changes.
Well, you're assuming exactly the state of affairs that this thread is
questioning...  The fact that the threat of changing things to this degree
has dredged up such polarized opinions should indicate that we ought to be
leaving things alone.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140611/f6c21c35/attachment.html>

More information about the es-discuss mailing list