Test appears to be suffering from changed stringification of floats#8
Closed
lizmat wants to merge 1 commit intoUtil:masterfrom
Closed
Test appears to be suffering from changed stringification of floats#8lizmat wants to merge 1 commit intoUtil:masterfrom
lizmat wants to merge 1 commit intoUtil:masterfrom
Conversation
As part of today's Squashathon, this module was [marked as having a problem](Raku/ecosystem-unbitrot#96). Turns out it was a single test that was testing on the stringification of a float. Since some work was done in that area recently, I assume that the changed stringification is the source of the problem, not different handling of floating point arithmetic itself. Hence this change of the test. Hope that's the right answer!
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As part of today's Squashathon, this module was marked as having a problem. Turns out it was a single test that was testing on the stringification of a float. Since some work was done in that area recently, I assume that the changed stringification is the source of the problem, not different handling of floating point arithmetic itself. Hence this change of the test. Hope that's the right answer!