Actually I think symbol name interference should be left as implementation detail. So I would change 19.4.1.1 § 2 to allow implementations for custom behavior.
On Tue, Oct 25, 2016 at 12:45 PM, Shahar Or <[email protected]> wrote: > So, we have function name inference, like > > ``` > const funcs = { foo: () => {} } > funcs.foo.name === 'foo' // true > ``` > > and this inference also works similarly with `const foo = () => {}` and > such. > > So, how about Symbol description inference, like: > > ``` > const symbols: { > foo: Symbol(), > bar: Symbol() > } > symbols.foo // Symbol(foo) > symbols.bar // Symbol(bar) > ``` > > and `const foo = Symbol()` and such? > > Here is my real use case: > https://github.com/yarom-and-shahar/cyclejs-shooter/blob/ > feaaf0ecd7620832b4bff90ab0f701d51ddcf3ff/src/ui-from-state/ > index.test.js#L22-L25 > > _______________________________________________ > 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
