Ashley Claymore

Does it make sense to add tests to ensure that `toSorted` and `toReversed` are not susceptible to `Array.prototype.{sort,reverse}` being patched? (e.g. An implementation similar to: `Array.prototype.toSorted = function(f) { return...

thanks @ljharb! Makes sense 😀

EDIT: DONE TODO: we should add a new test to cover yesterdays spec change https://github.com/tc39/proposal-change-array-by-copy/issues/85 maybe something like: ```js let userLandCodeCalled = false; const arr = new Uint8Array(2); const nonPureValue...

fyi @bathos I've created a corresponding issue in 402 too: https://github.com/tc39/ecma402/issues/686

Some more info here on Jest's custom test runner: https://www.youtube.com/watch?v=NtjyeojAOBs "ReactiveConf 2017 - Rogelio Guzman: Jest as a Platform"

This appears to have been fixed by #467

One potential reason why this could be particularly 'dangerous' is that it's required to specify the assertion types to ensure they impact CFA. ```ts type TypePredicate = (v: unknown) =>...

Hi @lin72h here are the [notes](https://github.com/tc39/notes/blob/main/meetings/2022-11/nov-30.md#records-and-tuples) and [slides](https://docs.google.com/presentation/d/1nJFe5aIT4RO9_MyVgc7zqyv4C12Pv6GPee77ATHzS_g/) for R&T from the last TC39 plenary (Nov 2022). One of the current concerns is from implementers on the technical challenges of...

Some of the reasons for choosing `with` were brevity and also because of the similarities to [its use in the Temporal proposal](https://tc39.es/proposal-temporal/#sec-temporal.plaindate.prototype.with).

One other reason for retaining the `splice` part of the name is so they both appear in auto complete. If someone types `arr.splice` they are likely to see both `splice`...