Suggestion: Array.prototype.sort - remove the need for compareFn to handle undefined values

Search Terms

Array.prototype.sort undefined, Array.prototype.sort, sort undefined, extends undefined ? never : T, Array prototype sort, Array.prototype

Suggestion

Based on my understanding of the JS spec the Array.prototype.sort compareFunction is never called on undefined values in an array (they are always sorted to the end of the array).

all undefined elements are sorted to the end of the array, with no call to the compareFunction
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort

However, currently the inputs of the compareFn have the type T where T is the types of values in the array. Which forces the developer to make their compare function handle undefined values, despite the compare function never being called with undefined values.

Current

sort(compareFn?: (a: T, b: T) => number

Suggested

sort(compareFn?: (a: T extends undefined ? never : T, b: T extends undefined ? never : T) => number

Use Cases / Examples

The below which is not currently valid would now be valid.

[1, undefined, 2].sort((a: number, b: number) => a - b)

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

Commencez par la déclaration TypeScript de Array.prototype.sort et comparez son paramètre compareFn avec le comportement d’ECMAScript décrit dans l’issue. Vérifiez comment le type conditionnel proposé affecte les tableaux contenant undefined, l’inférence du callback et les typages existants, puis validez l’exemple suggéré. C’est terminé lorsque le callback prévu est accepté sans modifier le comportement à l’exécution ni introduire de problèmes de compatibilité involontaires.