| 06:28 | <sideshowbarker> | Are there tests somewhere for https://github.com/tc39/proposal-regexp-legacy-features/ ? I’m looking in https://github.com/tc39/test262 and not finding anything — but maybe I’m not looking in the right place. e.g., looking in https://github.com/tc39/test262/tree/main/test/built-ins/RegExp I’d naïvely expect to find some test for |
| 06:54 | <Domenic> | sideshowbarker: the cursed annex B division strikes again, https://github.com/tc39/test262/tree/main/test/annexB/built-ins/RegExp/legacy-accessors |
| 06:54 | sideshowbarker | looks |
| 06:54 | <Domenic> | There, uh, appear to be no actual tests of the functionality... |
| 06:55 | <Domenic> | Just tests that it doesn't work in some situations |
| 06:55 | <Domenic> | Possibly that's why it's stuck at stage 3 |
| 06:56 | <littledan> | yeah tests and implementation priority (I guess it goes both ways) |
| 06:56 | <littledan> | I mean, engines implement legacy accessors, but I don't know if they implement the cleanups proposed |
| 06:56 | <Domenic> | Not sure how up to date https://github.com/tc39/proposal-regexp-legacy-features/blob/master/changes.md is |
| 06:57 | <littledan> | ES6 made some limits on how bad the legacy accessors could possibly be, and the proposal spells things out in an even "cleaner" way than that |
| 06:57 | <littledan> | yeah I don't know either, I haven't been following browser changes here |
| 06:58 | <littledan> | so, yeah, if someone wants a project, that's up for grabs and there's a clear way forward |
| 06:58 | <littledan> | namely, write the tests, assess which browsers already do those semantics, and maybe implement in a browser and convince them to ship |
| 10:59 | <sideshowbarker> | now looking for Array.p.group tests, and not finding any in https://github.com/tc39/test262/tree/main/test/built-ins/Array/prototype |
| 12:03 | <Ashley Claymore> | Looks like they are still in PR https://github.com/tc39/test262/pull/3354 |
| 12:03 | <Ashley Claymore> | https://github.com/tc39/test262/pull/3353 |
| 15:10 | <bakkot> | we should get those merged |
| 15:10 | <bakkot> | the submitter probably isn't gonna come back at this point so someone else will need to pick those up |