We don't yet have a mechanism for built-in modules, and that's not going to be an obstacle for continuing to improve the language.
As soon as a viable mechanism and precedent exists for that, new things very well might only be added via that mechanism, rather than solely by adding new global things. On Tue, Aug 16, 2016 at 6:52 PM, /#!/JoePea <[email protected]> wrote: > Seems like when the ES6 Modules became official that it would be a good > idea to *not* define more globals in the language, and instead spec things > to be modules, f.e. something like: > > ```js > import {apply} from 'Reflect' > // insead of > const {apply} = window.Reflect > ``` > > This would also be a pattern for programs that use the JS engine to follow: > > ```js > import {define} from 'CustomElements' // in browsers > // instead of > const {define} = window.customElements > ``` > > Maybe a symbol would be needed for any modules that are native? > > ```js > import {define} from '#CustomElements' // # means native module > ``` > > */#!/*JoePea > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
