Repository navigation
docs(ion-1-1): optimize fixed-size decimal encoding for common cases - #416
Merged
Merged
Conversation
tgregg
approved these changes
Oct 16, 2026
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.
Issue #, if available:
None
Description of changes:
Changes the binary encoding of small decimals in the Ion 1.1 spec so the exponent is a fixed 1-byte
FixedIntinstead of a variable-widthFlexInt.This reduces branching by eliminating the FlexInt for common case decimals (exponent in -128..127 inclusive)
Encoded size is 1 byte smaller when the exponent is in -128..-65 or 64..127, but one byte larger for exponents outside -128..127.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.