Re:Rust for C++ programmers – part 3: primitive types and op...
by repsilat on Wednesday April 23, 2014 @04:00AM
(#7632730)
Add me to the list. The other day I was debugging some simple Python code that worked something like
return 10000 if x > 10000 else x
and it wasn't working because x was a string. Instead of raising an exception, though, Python decided that all strings are "greater than" all integers, and code was essentially equivalent to return x
Re:Rust for C++ programmers – part 3: primitive types and op...
by masklinn on Wednesday April 23, 2014 @04:54AM
(#7632908)
> Instead of raising an exception, though, Python decided that all strings are "greater than" all integers
Yep. That's one of the things they changed/fixed in Python 3, comparisons are not defined across and between any and all types:
>>> "foo" > 3
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: unorderable types: str() > int()
Turns out the package expected numbers, but sometimes a bug meant the data source would give arrays (of a single number each), the package's own max (using <) would perform a lexical comparison (comparison would coerce to string and a graph with a value at 800 and one at 1800 would pick a y-scale for 800 and cut off 1800) but further operations would coerce to number, so there was no error anywhere and most graphs looked correct.