ModuleImport

Calvin Metcalf calvin.metcalf at gmail.com
Wed Jun 25 08:39:17 PDT 2014


    import 'foo'
    let foo = this.get('foo')

 that was what came out of the last meeting to replace module/from semantics

the payoff is decoupling how something is imported from how something is
exported.  A module is a bag of names, but there is no reason an import has
to be as well.




On Wed, Jun 25, 2014 at 11:15 AM, Kevin Smith <zenparsing at gmail.com> wrote:

>
>     import 'foo'
>>>     let foo = this.get('foo')
>>>
>>
> To be less flippant, this isn't a solution to the problem:  how do I
> statically bind to a module instance object?  It's a runtime workaround.
>
> Default-default aside, what's the payoff in trying to obscure the fact
> that a module is always a named set of exported bindings?
>
>


-- 
-Calvin W. Metcalf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140625/422b1515/attachment.html>


More information about the es-discuss mailing list