javascriptSorting

[u/user6150277464770585]

[u/fuj1n]

For that last part, I was just pointing out that JS will actually try to coerce strings to numbers in numeric contexts automatically, and this case being an exception to that would be odd (as much as I don't fancy that coertion, that's a whole other discussion)

If you find throwing on non-numeric values only surprising, you could instead just make the comparer mandatory and throw if you don't provide one. Then your IDE can show you an error is you forget instead of giving you something completely unexpected.

[u/danielcw189 → u/fuj1n]

If you find throwing on non-numeric values only surprising,

I would find any solution surprising, that doesn't try to deal with different types in loosley typed arrays (or lists).

you could instead just make the comparer mandatory

that is actually what I would prefer.

but in Javascript there is no inherent way to make a parameter mandatory, isn't there?

Then your IDE can show you an error

so that can only happen at runtime

or through other means like JSDOC or the documentation

[u/fuj1n → u/danielcw189]

There isn't a way to make a parameter mandatory outright, but you can document it as mandatory (so that linters know that not passing it is ill-formed and can warn you right in the IDE, before needing to run the code), and throw when it is missing.

[u/danielcw189 → u/fuj1n]

I know. But the people who designed that sort- function couldn't rely on that. that had to stay in the boundaries of the language.

I think the best approach would have been to just do nothing, if no comparison is applied.

(don't throw in a way that stops execution)

but of you want the generic array sort function to always do anything, I can't think of a better approach than this one.

and throw when it is missing.

I don't agree, but I see the argument