On Thu, Oct 31, 2013 at 11:06 AM, Erik Arvidsson
erik.arvids...@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
On Oct 31, 2013, at 8:06 AM, Erik Arvidsson erik.arvids...@gmail.com wrote:
Make sense but I'm not sure it is needed/desired.
I agree, actually, despite being the one who put it in there in the first
place. I originally intended it as a convenience e.g. for quick scripts. But by
itself it's
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@mozilla.org
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.arvids...@gmail.com wrote:
Both the wiki and the ES6 draft have the following as valid
Make sense but I'm not sure it is needed/desired.
Where is this documented?
On Thu, Oct 31, 2013 at 10:39 AM, Sam Tobin-Hochstadt
sa...@cs.indiana.eduwrote:
This exports all of the declarations defined in the current module. So:
```
let x = 1;
class foo {};
export *;
```
exports both
Looking at harmony modules[1], I wanted to get some clarification on
the order of export, module and such in a module's body.
Looking at the Syntax section, this section:
ModuleElement(load) ::= Statement
| VariableDeclaration
| FunctionDeclaration
All exports of all declared/required modules are computed before execution
starts. So it doesn't matter what order things run in, you won't get any no
such export errors if you import a valid export.
Dave
On May 19, 2011, at 2:13 PM, James Burke wrote:
Looking at harmony modules[1], I wanted
7 matches
Mail list logo
