| 00:54 | <bakkot> | rkirsling: this is one of the older known flaws in the spec; see e.g. https://github.com/tc39/ecma262/issues/467 |
| 00:55 | <bakkot> | there have been some recent attempts to improve the situation e.g. https://github.com/tc39/ecma262/pull/2267 |
| 00:55 | <bakkot> | although with their own issues e.g. https://github.com/tc39/ecma262/issues/2659 |
| 00:55 | <bakkot> | for your specific issue https://github.com/tc39/ecma262/pull/2205 is the best reference probably |
| 00:56 | <bakkot> | if you feel inclined to figure out what exactly web reality is, and how to write that down, most everyone would be happy with such a PR I think |
| 00:57 | <bakkot> | don't know that there would be much appetite for going the other way and trying to get implementations to match the spec |
| 01:18 | <rkirsling> | cool |
| 01:44 | <rkirsling> | I'm not sure if I fully understand where that ended up at a glance but I suppose i could have a chat with shu about it |
| 13:02 | <ryzokuken> | is there a FlatList operation somewhere? |
| 15:10 | <Jack Works> | Apply(%Array.prototype.flat%)? |
| 15:11 | <ryzokuken> | would that work on ECMAScript List thingies? |
| 15:11 | <Jack Works> | No |
| 15:12 | <ryzokuken> | that's what I was looking for |
| 15:29 | <jmdyck> | So the input would be a List whose elements could themselves be Lists? |
| 15:30 | <littledan> | It would be cool to have the full set of stuff like https://infra.spec.whatwg.org/ in ECMA-262. But they don't seem to have List flat either. |
| 16:09 | <ryzokuken> | So the input would be a List whose elements could themselves be Lists? |
| 16:09 | <ryzokuken> | and a FlatList AO that would flatten it into a flat (?) list |
| 16:11 | <jmdyck> | I think a List-of-(possible)-Lists doesn't really happen in the current spec. |
| 16:11 | <ryzokuken> | not so far, but I'm dropping some hot spec text atm 🙈 |
| 16:11 | <ryzokuken> | it's for a proposal, but the point still stands I guess |
| 20:56 | <bakkot> | would anything important break if we made Array.prototype and Object.prototype reject numeric properties, do you figure |
| 20:57 | <bakkot> | that is, making them a new kind of exotic object which would silently (or loudly, I guess) prevent adding properties which could be array indices |
| 21:55 | <shu> | oh man |
| 21:56 | <littledan> | Can we fix the override mistake in all cases except the one lodash runs into at the same time? |
| 21:56 | <littledan> | I mean, an exotic object can have a different kind of Set() |
| 22:13 | <bakkot> | what's the one lodash runs into? |
| 22:15 | <littledan> | (I don't remember the details offhand) |
| 23:18 | <Domenic> | It would be cool to have the full set of stuff like https://infra.spec.whatwg.org/ in ECMA-262. But they don't seem to have List flat either. |
| 23:19 | <Domenic> | No need to copy it over, specs are allowed to reference other specs. |
| 23:19 | <littledan> | I wouldn't mind adopting the sentence-based notation that infra uses, tbh |
| 23:28 | <TabAtkins> | it is very nice to use in practice |