| 16:16 | <snek> | can we get a TypedArray.prototype.equals |
| 17:12 | <bakkot> | do you ever need that outside of tests? |
| 17:12 | <bakkot> | I have never needed that outside of tests |
| 17:44 | <Michael Ficarra> | what's it matter? people writing tests are valid users of the language |
| 18:22 | <bakkot> | I am generally opposed to adding features to browsers which will not be used in browsers |
| 18:22 | <bakkot> | I am happy to have it in WinterCG or whatever |
| 18:29 | <Michael Ficarra> | does WinterCG add prototype methods to existing built-ins? |
| 18:36 | <bakkot> | no reason they couldn't but also they could just add assert.equals and define its behavior for TAs |
| 18:36 | <bakkot> | or whatever |
| 21:47 | <ljharb> | we could certainly add a feature as normative optional, and HTML could make it prohibited in browsers |
| 22:47 | <Justin Ridgewell> | I have never needed that outside of tests |
| 23:41 | <Justin Ridgewell> | Or there’s another usecase for comparing values stored in History State, to detect the changing UI values. |
| 23:41 | <Justin Ridgewell> | So used it twice in prod in the last 3 months. |
| 23:51 | <Rob Palmer> | (Android Element client is dropping content. Jordan's message is missing. I can observe it only if I click into it to reply.) |
| 23:52 | <Rob Palmer> | (And I swear I have not muted anyone) |
| 23:53 | <rkirsling> | Yeah I can confirm that |