Skip to content

math/big: handle additional edge cases for Rat #61531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mauri870
Copy link
Member

@mauri870 mauri870 commented Jul 22, 2023

New special cases have been added to the Rat testcase.
Updated the function quotToFloat32/64 to check for zero
as well when determining if the value is infinite. This
change ensures that the exact flag is correctly set for
these edge cases, preventing test failures.

Thanks Johan Jansons (@jupj) for the proposed fix on
the ticket description.

Fixes: #56164

New special cases have been added to the Rat testcases.
Updated the function quotToFloat32/64 to check for zero
as well when determining if the value is infinite. This
change ensures that the exact flag is correctly set for
these edge cases, preventing test failures.

Thanks Johan Jansons (@jupj) for the proposed fix on
the ticket description.

Fixes: golang#56164
@gopherbot
Copy link
Contributor

This PR (HEAD: a60f722) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/512198.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to register for Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

math/big: new examples that fail the checks in TestFloat64SpecialCases
2 participants