Name & scope of Tuple.prototype.* methods

[rricard]

As part of the stage 1 Change Array by Copy we are proposing changes to Tuple.prototype.* methods:

• Naming of those methods should be discussed in Names of functions proposal-change-array-by-copy#10 (current new candidate in New naming scheme: with<PastTense> and withAt proposal-change-array-by-copy#26)
• Limiting the number of Tuple.prototype.* methods is discussed in To change: Reduction of scope proposal-change-array-by-copy#27

If you do have opinions on the naming and methods available on Tuple, please go comment in those threads as we intend to centralize discussion there.

Thank you!

[rricard]

Locked in favor of discussing in tc39/proposal-change-array-by-copy#10 and tc39/proposal-change-array-by-copy#27

[rricard]

As it stands, we should implement the following (non-final) naming scheme to follow tc39/proposal-change-array-by-copy#28:

• Tuple.prototype.withFilled(value, start, end) -> Tuple
• Tuple.prototype.withCopiedWithin(copiedTarget, start, end) -> Tuple
• Tuple.prototype.withPopped() -> Tuple
• Tuple.prototype.withPushed(values...) -> Tuple
• Tuple.prototype.withReversed() -> Tuple
• Tuple.prototype.withShifted() -> Tuple
• Tuple.prototype.withSorted(compareFn) -> Tuple
• Tuple.prototype.withSpliced(start, deleteCount, ...items) -> Tuple
• Tuple.prototype.withUnshifted(...values) -> Tuple
• Tuple.prototype.withAt(index, value) -> Tuple

[rricard]

We now have to take in account the following reduction of scope: tc39/proposal-change-array-by-copy#27

This will result on the following Tuple prototype:

• Tuple.prototype.withReversed() -> Tuple
• Tuple.prototype.withSorted(compareFn) -> Tuple
• Tuple.prototype.withSpliced(start, deleteCount, ...items) -> Tuple
• Tuple.prototype.withAt(index, value) -> Tuple

[rricard]

Change array by copy went to stage 3 with an agreed scope. Tuple is going to follow this new scope. This is already in the spec text.