fix(std): reject "-0" forms in stringToLong (#1582)#1585
Merged
julien-truffaut merged 1 commit intoMay 14, 2026
Conversation
Member
|
Thank you! Approved |
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.
Fixes #1582.
stringToLong.getOption("-0")returnedSome(0L)butreverseGet(0L)is"0", so the Prism round-trip law fails for negative-zero forms (-0,-00,-01, ...). ExtendinputBreaksPrismLawswith a guard for any string starting with-0.Per @julien-truffaut in #1582 (comment) ("Thanks for the bug report ... Feel free to send a PR :)"), with the guard expression matching the suggestion in the issue. Added unit tests in
StringsSpecfor both the rejected and the still-accepted shapes.