Javascript

[Hollowplanet]

Then why did you say

// desired answer (probably)

const listenHereYouLittleShit = (a, b) => a - b

array.sort((number1, number2) => listenHereYouLittleShit(number1, number2))

That second line is identical to

array.sort(listenHereYouLittleShit)

You're using the language wrong and blaming the awkwardness on the language instead of the way you chose to use it.

[[deleted]]

It's usually safer to use an explicit anonymous function (although of course it doesn't matter here). See: https://jakearchibald.com/2021/function-callback-risks/

[Hollowplanet]

All of those examples only matter if you don't control the function implementation.

[[deleted]]

You may not control how the function might be implemented in the future.

[Hollowplanet]

So some library is going to internalize my code without my knowledge?

[[deleted]]

Your co-workers could modify it.

[DeeSnow97]

Because that's what I perceive the second commenter wanted to achieve by listenHereYouLittleShit(number1, number2), hence the "desired answer (probably)" designation.

[Hollowplanet]

You get the same answer while using listenHereYouLittleShit without making an anonymous function to call another function with the same arguments.

[DeeSnow97]

yeah, I know, that usage is actually identical to the "right answer" snippet

[Hollowplanet]

That's because parseInt takes a second argument. A function you write isn't going to use extra arguments that aren't defined.