chore: update uint256 to 1.3.0 and decimal to 1.4.0 #11471
Conversation
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
EVODelavega
approved these changes
Jul 17, 2024
Contributor
|
I've already had it in the upgrade to cometbft 1.0 |
EVODelavega
force-pushed
the
chore/update-nums-package
branch
from
ae345c4 to
4a171a7
Compare
Member
Author
|
@ze97286 I had closed that but actually reopening because:
|
Signed-off-by: Jeremy Letang <me@jeremyletang.com>
jeremyletang
force-pushed
the
chore/update-nums-package
branch
from
4a171a7 to
b4038a0
Compare
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.
I've just noticed that both the uin256 and decimal package have had recent (ish) updates, and both recent release comes with performances improvement. The codebase relying heavily on both of these, updating them can only be beneficial.