Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
I assume this is because that number is so large that it loses precision, in which case this is more of a quirk of floating point than a quirk of Python.
It’s both. As you said it’s because of loss of floating point precision, but it’s also with some of the quirks how Python compares int with float. These two together causes this strange behavior.
I assume this is because that number is so large that it loses precision, in which case this is more of a quirk of floating point than a quirk of Python.
Disclaimer: Have not read the article yet.
It’s both. As you said it’s because of loss of floating point precision, but it’s also with some of the quirks how Python compares int with float. These two together causes this strange behavior.