Int division `bottom / (-1)` exceeds 32bit integers range

Open
#317 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
backend

Research direction

Start by locating the JavaScript implementation of EuclideanRing integer division and compare it with the quot implementation in purescript-integers, which the issue says normalizes with | 0. Check the relevant division tests and add coverage for bottom / (-1); done when the result stays within the signed 32-bit Int range.

Written by the indexing model from the issue text.

Description

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.

Dominant language
PureScript
Stars
168
Forks
90
Avg merge
3d 1h
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from purescript/purescript-prelude

All issues in purescript/purescript-prelude

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.