Script: ulong via fields API (#76519) #76613
Merged
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.
Exposes unsigned long via the fields API.
Unsigned longs default to java signed longs. That means the upper range
appears negative. Consumers should use
Long.compareUnsigned(long, long)
Long.divideUnsigned(long, long)
andLong.remainderUnsigned(long, long)
to correctly work with values known to be unsigned long.
Alternatively, users may treat the unsigned long type as
BigInteger
usingthe field API,
field('ul').as(Field.BigInteger).getValue(BigInteger.ZERO)
.This change also implements the beginning of the converters for the fields
API. The following conversions have been added:
Backport: aea8bff