Re:Statically-typed error handling in Python using Mypy
by staticassertion on Sunday December 08, 2019 @05:44PM
(#21738954)
> When you order two incompatible types where neither is numeric, they are ordered by the alphabetical order of their typenames:
????????
Re:Statically-typed error handling in Python using Mypy
by detaro on Sunday December 08, 2019 @08:51PM
(#21739833)
That's entirely an implementation detail. The thing that matters for programmer experience is the specification of behavior: There's going to be an arbitrary order. You certainly can argue that you think it would be less surprising if trying this just failed, or that promising a stable order ties down implementations too much, but I don't think providing an order is that surprising.
None (as far as I remember) of the common "wat" examples about JS are interpreter implementation details, but specified behavior.
I'm mildly curious why CPython chooses to implement it this way, but if I had to guess: I'm assuming it is to provide a stable order between objects of different classes with the same hash() value. Hash-value being what I suspect is what the quoted answer misrepresents as "their address" (the address being in CPython the default fallback for objects that do not implement a hash() function), and being a good candidate to establish an arbitrary order.
Re:Statically-typed error handling in Python using Mypy
by staticassertion on Monday December 09, 2019 @01:52AM
(#21740870)
Sorry, I'm not sure I understand at all the difference between this and the 'wat' stuff.
Re:Statically-typed error handling in Python using Mypy
by icebraining on Sunday December 08, 2019 @08:32PM
(#21739774)
That's just GIGO. There's simply no good way to order "two incompatible types where neither is numeric".
Seems like a completely reasonable thing to do?