You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've built the uint256 library a long time ago, but never really got around to using it outside of the EVM. This is a shame, as the library is more performant than big.Int as well as more "correct", as in we don't need to special case overflows and negative numbers.
Whilst it might be non-trivial to switch certain parts of Geth over while keeping backwards compatibility, one place that might be less gnarly is the statedb internals. We kind of expect that some things might leak out, but statedb is not really something many people use API wise and it might help to do some cleanups there.
The text was updated successfully, but these errors were encountered:
karalabe
changed the title
uint256: switch over the statedb package from big.Int to uint256.Int Item statusDraft karalabe
uint256: switch over the statedb package from big.Int to uint256.Int
Nov 23, 2023
We've built the uint256 library a long time ago, but never really got around to using it outside of the EVM. This is a shame, as the library is more performant than big.Int as well as more "correct", as in we don't need to special case overflows and negative numbers.
Whilst it might be non-trivial to switch certain parts of Geth over while keeping backwards compatibility, one place that might be less gnarly is the statedb internals. We kind of expect that some things might leak out, but statedb is not really something many people use API wise and it might help to do some cleanups there.
The text was updated successfully, but these errors were encountered: