banned VS proposal-change-array-by-copy

I don't care about being banned. Wouldn't be the first time https://github.com/guest271314/banned.

Or, more accurately, the "teams" I have joined have tended to get all bent out of shape when their narratives are questioned, and their errors and omissions are exposed on the record - so they have banned me and just closed my issues. E.g., https://github.com/guest271314/banned. Being banned from Node.js organization - after being invited to join the single executable "team" - was ridiculous.

On the other side of that coin, there are some developers who think their code is high and mighty to the degree that if/when you question their specification goal/non-goal narrative, point out ambiguity relevant to the third-party code they promote, or advise them the configuration process for their work is unnecessarily complicated, when JSON could be used they'll ban you. Ask me how I know https://github.com/guest271314/banned.

Like, he's his essay complaining that he can't post racial slurs on Github. https://github.com/guest271314/banned/issues/2

Yes, the Deno folks banned me. So did the Node.js folks, and many others https://github.com/guest271314/banned. Weak. I ain't mad. I vet spurious claims, without exception. I don't care who you think you are. Your claims are not above or below being tested and vetted, exposed.

If you are going to take the time to ban https://github.com/guest271314/banned/issues/7 the messenger that delivers the message you are advertising false claims you must have enough time to review third-party claims in advance.

Well, those are not viable reasons to be kicked off of a team, so they had to lie and say I "attacked" another user. Then lie some more and claim I "harassed" another user. https://github.com/guest271314/banned/issues/6

Most if not all of those bans should be documented here https://github.com/guest271314/banned.

The new change array by copy methods (ES2023) will also work with tuples. So while you can't

Change Array by Copy

Stage 3 Change array by copy proposal offers methods like sortTo() that return a new array instead of mutating the original.

Note: there's a stage 3 proposal that introduces copy = arr.toSorted().

Change Array by Copy: Provides additional methods on Array.prototype and TypedArray.prototype to enable changes on the array by returning a new copy of it with the change.

The proposal is described here, with the other methods being:

Proposal, Polyfill

You're unlikely to see any new methods being added to JavaScript's Array that would modify an array in place like reverse() and sort() do. In fact some of the new methods that are being added are versions of reverse() and sort() (and splice()) that create copies rather than modifying the originals. Read more about them here: Proposal: Change Array by copy.

Since cloning is so common, a new specification has been written which has reached stage 3, which will give us a host of new ways to copy and then change an array. This proposal is called the "Change Array by Copy" proposal. Let's take a look at how it works.