domenic at domenicdenicola.com (2013-11-02T19:20:23.509Z)
On Thu, Oct 31, 2013 at 11:06 AM, Erik Arvidsson <erik.arvidsson at gmail.com> wrote: > Make sense but I'm not sure it is needed/desired. It's very useful for convenience libraries, quick refactorings, etc. In other languages, I use it a lot. > Where is this documented? It's very briefly described in the wiki page, and fully specified in the spec documents in the js-loaders repository https://github.com/jorendorff/js-loaders (although there's lots of churn in some parts of those documents).
On Thu, Oct 31, 2013 at 11:06 AM, Erik Arvidsson <erik.arvidsson at gmail.com> wrote: > Make sense but I'm not sure it is needed/desired. It's very useful for convenience libraries, quick refactorings, etc. In other languages, I use it a lot. > Where is this documented? It's very briefly described in the wiki page, and fully specified in the spec documents in the js-loaders repository https://github.com/jorendorff/js-loaders (although there's lots of churn in some parts of those documents). Sam > > > On Thu, Oct 31, 2013 at 10:39 AM, Sam Tobin-Hochstadt <samth at cs.indiana.edu> > wrote: >> >> This exports all of the declarations defined in the current module. So: >> >> ``` >> let x = 1; >> class foo {}; >> export *; >> ``` >> >> exports both `x` and `foo`. >> >> Sam >> >> On Thu, Oct 31, 2013 at 10:02 AM, Erik Arvidsson >> <erik.arvidsson at gmail.com> wrote: >> > Both the wiki and the ES6 draft have the following as valid >> > ExportDeclaration: >> > >> > export * >> > >> > (without a `from ModuleSpecifier`) >> > >> > What is the intended semantics for that? >> > >> > -- >> > erik >> > >> > _______________________________________________ >> > es-discuss mailing list >> > es-discuss at mozilla.org >> > https://mail.mozilla.org/listinfo/es-discuss >> > > > > > > -- > erik