Repository navigation
Conversation
toprameen
marked this pull request as ready for review
November 19, 2026 00:30
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
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.
Nat.readnow short-circuits its length check when it sees a 16th character after trimming leading zeros. Inputs with exactly 15 characters still compare against the maximumNat.In a local benchmark of 100,000 reads of a 128-digit field, native C went from 43 ms to 3 ms, Bun from 36 ms to 31 ms, and Node from 68 ms to 21 ms. Near the cutoff, Bun took 32 ms instead of 17 ms for 100,000 reads of a 16-digit field.
Existing parser fixtures pass, and BendTT verifies that the old and new readers return the same result for every
String.