include

Sam Tobin-Hochstadt samth at cs.indiana.edu
Mon Jul 14 18:24:05 PDT 2014


Why not:

    import {} from 'foo';

or

    import * as f from 'foo';

This is assuming that there are no other desired exports -- if there
are, then the case is even easier.

Sam

On Mon, Jul 14, 2014 at 8:37 PM, John Barton <johnjbarton at google.com> wrote:
> In the module system we issue
>    import {foo} from 'foo';
> and the Loader computes an address, say foo.js, fetches the resource and
> compiles it. If the content of foo.js has no dependencies, it is evaluated,
> then the importer is evaluated. Yay!
>
> Now suppose that foo.js defines a global value. Oh bad sure, but sometimes
> you have to play cards you are dealt. We still depend upon foo.js, bad or
> not bad.
>
> In the current module system we have to abandon ship. In our importer we
> need to:
>   // WARNING pre-load foo.js somehow!
>
> Now imagine if we could issue
>    include 'foo';
> and the Loader computes an address, say foo.js,fetches the resource and
> compiles it. Since the content has no dependencies, it is evaluated, then
> the importer is evaluated. Yay!
>
> On now back to preloading somehow,
> jjb
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>


More information about the es-discuss mailing list