I found a potential bug in EuclideanRing.
In PureScript, Int is defined as a signed 32-bit integer, but evaluating bottom / (-1) results in 2147483648, which exceeds the 32-bit range.
I think the JS implementation for integer division should include | 0 normalization to fix this.
cf: This issue doesn't occur with truncating division quot defined in purescript-integers, as it correctly includes | 0.
I found a potential bug in
EuclideanRing.In PureScript,
Intis defined as a signed 32-bit integer, but evaluatingbottom / (-1)results in2147483648, which exceeds the 32-bit range.I think the JS implementation for integer division should include
| 0normalization to fix this.cf: This issue doesn't occur with truncating division
quotdefined in purescript-integers, as it correctly includes| 0.