Re: Property names for public symbols

[Axel Rauschmayer]

Can you explain what you mean by “same-named”? You want `Symbol.for()` to have 
the same casing as `Symbol.iterator`?


 On 07 Feb 2015, at 02:17, Brendan Eich bren...@mozilla.org wrote:
 
 Some tasteful inconsistency (the hobgoblin of big minds) is required here. We 
 want the well known symbols' names as static properties of Symbol to be 
 same-named.
 
 /be
 
 Mark Volkmann wrote:
 Agreed, like at the constants on the Math object.
 
 ---
 R. Mark Volkmann
 Object Computing, Inc.
 
 On Feb 6, 2015, at 12:39 AM, Axel Rauschmayer a...@rauschma.de 
 mailto:a...@rauschma.de wrote:
 
 I know that this is a small nit and that it’s probably too late, but: 
 Shouldn’t public symbols (`Symbol.iterator` etc.) have all-uppercase 
 property names? It would indicate that they are constants and it would 
 visually set them apart from other stuff that is in `Symbol` 
 (`Symbol.for()` etc.).

-- 
Dr. Axel Rauschmayer
a...@rauschma.de
rauschma.de



___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Re: Property names for public symbols

[Brendan Eich]

Axel Rauschmayer wrote:
Can you explain what you mean by “same-named”? You want `Symbol.for()` 
to have the same casing as `Symbol.iterator`?


No, I mean we would normally use iterator (and had __iterator__ in 
SpiderMonkey, then '@@iterator' I believe), not ITERATOR. Python's 
dunder-bracketing doesn't cut it, symbols win. But UPPERCASE loses.


/be
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss