Fix DividingCoder buffer size under-allocation for large inputs - #27
Merged
Conversation
Compute reduction factor as a double (log2(L)/8) and use Ceil for safe encode/decode sizes instead of a truncated 1000-scaled integer, which lost precision and under-allocated the decode buffer on long, high-value strings. Add standalone DividingCoderTests covering edge-buffer roundtrips (0xFF, zero, leading-zero patterns) and a size-sufficiency regression guard across Base58/Base62/Base36; update the Base58 safe-char-count expectation.
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
1 participant
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.
Compute reduction factor as a double (log2(L)/8) and use Ceil for safe encode/decode sizes instead of a truncated 1000-scaled integer, which lost precision and under-allocated the decode buffer on long, high-value strings.
Add standalone DividingCoderTests covering edge-buffer roundtrips (0xFF, zero, leading-zero patterns) and a size-sufficiency regression guard across Base58/Base62/Base36; update the Base58 safe-char-count expectation.