Integer serialization fix for 32 bit platform compatibility #52
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.
Motivation:
RFC 9651 permits serializing an integer in the range of -999,999,999,999,999 to 999,999,999,999,999 inclusive (Section 4.1.4-2.1.1). As
RFC9651BareItem
takes valuesinteger
ordate
with an associated value of typeInt
, that range is implicitly more constrained on 32-bit platforms to a subset range ofInt32.min
toInt32.max
inclusive.Modifications:
RFC9651BareItem
to take valuesinteger
ordate
with an associated value of typeInt64
instead, which is sufficient for the permitted range.Result:
Compatibility for the Integer and Date Structured Types on 32-bit platforms.