fix(cast): consistent serialization of Uint/Ints depending on actual type#14824
Open
0xferrous wants to merge 2 commits into
Open
fix(cast): consistent serialization of Uint/Ints depending on actual type#148240xferrous wants to merge 2 commits into
0xferrous wants to merge 2 commits into
Conversation
0xferrous
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr,
mattsse and
zerosnacks
as code owners
0xferrous
force-pushed
the
push-rtzzspzvvklr
branch
2 times, most recently
from
c50f267 to
84c1f3d
Compare
zerosnacks
reviewed
May 19, 2026
zerosnacks
left a comment
zerosnacks
left a comment
Contributor
There was a problem hiding this comment.
Hi @0xferrous, thanks for the PR! Apologies the other one went stale.
Some notes, overall lgtm 👍
0xferrous
force-pushed
the
push-rtzzspzvvklr
branch
from
84c1f3d to
4bb7bcf
Compare
Contributor
|
This pull request is stale because it has been open for 14 days with no activity. It will be closed in 7 days if there is no further activity. |
…type The current implementation dynamically tries to determine if the runtime value can fit in 64 bits, but this leads to inconsistent serialization. For instance if you were decoding an `uint[]`, some of the values that fit in 64 bits will serialize as number while others serialize as string making it require special handling on the user that is consuming the json. This change makes it so it uses the type information to determine the serialization. So the user will always know that specific types will always serialize to a number or a string depending on the number of bits that type uses.
figtracer
force-pushed
the
push-rtzzspzvvklr
branch
from
4bb7bcf to
edc13fe
Compare
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
3 participants
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
The current implementation dynamically tries to determine if the runtime value can fit in 64 bits, but this leads to inconsistent serialization. For instance if you were decoding an
uint[], some of the values that fit in 64 bits will serialize as number while others serialize as string making it require special handling on the user that is consuming the json.Solution
Use the type information to determine the serialization. So the user will always know that specific types will always serialize to a number or a string depending on the number of bits that type uses.
PR Checklist