Re-port new integer-scanning utility methods #127
Merged
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
This may help prevent ArrayIndexOutOfBounds randomly seen in CI. See ruby#125
* Parse base should be from current pointer so add that to the get calls. * Pull out ascii check into util method. * Rename curr local var to ptr to better match C version.
This is to align the base10 code with the freshly-ported base16 code. See ruby#125
It does inside |
Aha, so it does! I will tweak this to move the final integer parse and |
This aligns with C code that does the final parse and curr update in strscan_parse_integer.
|
Thanks! |
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.
This is a re-port of the C code from @byroot for fast base 10 and base 16 integer scanning.
In #125, @kou pointed out there's an intermittent failure in the JRuby extension. We were unable to confirm exactly the circumstances that cause that failure, but this re-port should at least help reduce the change it is a bug in the original Java code.