How did we let this abomination become the language of the web anyway?pic.twitter.com/dI1SkWKT4i
-
There *is* a natural sort order for *homogeneous* untyped collections. Heterogeneous untyped collections should raise an error (something which Python 2 didn't do and Python 3 fixed). Coercing to strings by default is batshit insane.
The only reasonable implementation of untyped array sort is to *do what the comparison operators do*. That's what all versions of Python do (Py3 just doesn't allow comparing disparate types, Py2 does). Javascript does not. That makes *no* sense.
-
-
Your view is blurred by the habit of "adult" languages
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
what happens if the comparison operators don't produce a strict weak ordering? Like, throw a NaN in there, then what? (probably "error" is the sane thing)
-
It breaks. Basically sort is only defined if comparison is well-behaved, and NaN has ill-behaved (but non-erroring) comparison by IEEE spec, unfortunately. >>> sorted([2.0, float('nan'), 1.0]) [2.0, nan, 1.0] I can't really think of a fix without a special-case kludge for NaN.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.