Darien Maillet Valentine
Darien Maillet Valentine
You may wish to jump right to 8 while you're at it. The node-unicode-data project folks have already released the new module: https://github.com/mathiasbynens/unicode-8.0.0
The removal of the “the” in “refer to the indicated part” below seems like it was probably unintentional. Couldn’t figure out how to attach a comment inline on Github (which...
The issue here is narrower than I’d realized: per @joyeecheung, these failure cases occur only when using computed property syntax, and a minimal example demonstrating this was given in the...
As I researched this further hoping to facilitate triaging the issue, I came across [some interesting discussion](https://github.com/tc39/ecma402/pull/84) where many people shared different opinions about the scope of the symbol. The...
(It seems safe to at least rule out “per realm” being a typo in the spec: it’s explicitly defined as and referenced as the-value-of-a-slot-of-a-specific-%Intl%-object, which is a rather specific thing...
> Indeed typically the only per-realm symbols are well-known ones, on Symbol. Hm, am I using the term incorrectly? “Unless otherwise specified, well-known symbols _[sic]_ values are shared by all...
Cool, that was my understanding. FWIW an interesting twist in the discussion thread where folks debated the symbol’s scope was that it [was pointed out](https://github.com/tc39/ecma402/pull/84#issuecomment-282088004) that a scoped-to-each-realm symbol would...
@gibson042 I’m thrilled to hear this should be the case. I couldn’t find anywhere in the spec that seemed to mandate this, though. If it is already specified that this...
Anecdotal, @annevk, but personally I try to use the non-existent `appendAll` a few times a year. (Certainly not a big nuisance that it’s absent — just surprising, I think, if...
Yes — I missed that in the OP, the method I keep imagining exists is `appendAll(key, values)`, though I can see the utility of an entries-consuming method.