Given that you need to import symbols, I prefer explicit declarations (which will also be used for exporting).
On Oct 11, 2012, at 23:41 , Kevin Smith <[email protected]> wrote: > Hi all, > > ES6 is shaping up quite nicely. The last big area which I feel is still > quite foggy is syntactic support for symbolic property names, which Allen has > addressed with his at-names proposal. Perhaps syntax won't make it into ES6 > regardless of the work we do, but I think the symbol "story" isn't finished > until we've got something. > > With that in mind, I've created a sketch of an alternative at-name syntax > story. I've tried to include enough detail to show that it might work, but > not so much that I never finish the sketch : ) > > The basic idea is that modules implicitly define symbol namespaces. Symbols > can be imported from other modules, or from a "world" symbol map which > contains interned symbols for the entire execution environment. > > Read on: https://gist.github.com/3868131 > > The actual design sketch follows some initial examples. > > Thanks! > Kevin > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss -- Dr. Axel Rauschmayer [email protected] home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
