| 04:08 | <bakkot> | ArrayBuffer.prototype.resize has this carveout where hosts are allowed to throw instead of resizing, but we don't specify the kind of error they should throw https://tc39.es/ecma262/multipage/structured-data.html#sec-arraybuffer.prototype.resize |
| 04:09 | <bakkot> | I guess because they might throw an OOMError or something we don't specify? but it's a little odd |
| 17:05 | <peetk> | I'm working on speccing the new options bag approach for JSON.parseImmutable, and I'm wondering if there's any reason (besides brevity) that JSON.parse awkwardly reuses Evaluation (with some special "if this is JSON.parse" branches) rather than just having its own operation |
| 18:11 | <Chris de Almeida> | https://github.com/tc39/ecma262/issues/1681#issuecomment-526852584 |
| 18:31 | <Michael Ficarra> | (massive) pull requests welcome |
| 20:17 | <peetk> | ok i opened a PR but it's not at all massive... i suppose you'll tell me what i've missed :) |
| 20:43 | <bakkot> | the thing that would make it massive would be re-specifying the grammar |
| 20:43 | <bakkot> | just specifying the evaluation semantics is a nice middle ground IMO |