Fix Complex#to_s imaginary component sign for certain values
#12244
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HertzDevil
added
kind:bug
straight-shoota
approved these changes
Jul 15, 2022
straight-shoota
approved these changes
Aug 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some special values of a
Complex's imaginary component cause it to print an incorrect sign:-0.0→+ -0.0(should be- 0.0)+NaN→- NaN(should be+ NaN)-NaN→- -NaN(should be+ NaN)This PR fixes those edge cases by extracting the intrinsic sign with
Math.copysign.I don't think the rest of the standard library has the same issue, but this is something to keep in mind if we decide to implement
%+fetc. forString::Formatterin pure Crystal.