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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: improve serialization for errors and bigints #17282
feat: improve serialization for errors and bigints #17282
Changes from all commits
e90bd20
b1dac04
11ed4ab
0ea2e99
7333777
a5e9568
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In theory it can be optimized and we can write sections, but it requires a lot of work and our serialization optimized for numbers and strings (they are used more often than BigInts), also it will cause a big cache broken errors on CI (i.e. if you have cache from old webpack version and the new version of webpack can't deserialize because we will use new bytes for headers)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why it is storing as string:
writeBigInt64LE
, because BigInt can be longer than 64bitsthing.toString(16)
to reduce size, but I doesn't bring a lot of wins,4294967296n.toString(16)
->100000000
, also it will require to store sing (-/+) and will multiple on -1so storing them as string, I think, is the best solution
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Improved, now we bigints as int8 (when
n <= BigInt(127) && n >= BigInt(-128)
) and as int32 (whenn <= BigInt(2147483647) && n >= BigInt(-2147483648)
), other bigints we store as a string with ascii characters, so you can store any bigint