The optimised int/float comparison was accidentally not activated when the...
The optimised int/float comparison was accidentally not activated when the result of a comparison was already known to be of type bint (instead of a Python object), nor for the "!=" operator. These seem to be fairly common cases.
Showing
Please register or sign in to comment