[qoke]

Closes #17.

Ordering comparisons could lose precision by converting large integers to floating point. This made 9007199254740992 < 9007199254740993 return False, despite both values being within the supported integer range.

Integer operands are now compared without conversion. Mixed integer–float comparisons handle floating-point bounds and fractional components without first rounding the integer to a float.

Both regression cases, covering integer–integer and integer–float ordering, now match the Python reference results. The original failing Go results are included for comparison.

go test -count=1 ./... passes.

[ardan-bkennedy]

Thank you, @qoke, for reporting these issues and for providing proposed fixes. We reviewed all nine reports and used your suggestions where they made sense in the codebase. All nine issues have now been resolved in #34, each with corresponding regression tests, and the fixes are published in v1.11.0.

The issue addressed by this PR (#17) is covered by that release, so we are closing this PR in favor of the consolidated fix.

For future reports, please start with issues only so we can discuss the approach before opening pull requests. Thanks again for helping improve the project.