Add support for ruint as the uint256 backend
The ruint crate is known to be more performant in certain situations. So give it a try! It can be enabled by the ruint feature flag:
- If no feature flag is set (same as now), then
primitive-typesuint256 will continue to be used. - If the
ruintfeature flag is set, thenruintuint256 will be used.
evm = { version = "1.1.0", features = ["ruint"] }
In addition, evm::uint now contains re-export of H256, H160 and U256.
Fixes
- Fixed an issue of
generic-array's deprecated flag breaking build.
Detailed changelog since evm-v1.0.0
- Add a few more badges by @sorpaas in #380
- Fix typo by @sorpaas in #381
- chore(ci): upgrade checkout to v5 by @ozrg in #384
- chore: fix typos in comments and error messages by @GarmashAlex in #386
- docs: fix typos by @VolodymyrBg in #387
- chore: fix grammatical issues by @MozirDmitriy in #388
- chore: fix typo in comment in "another" by @gap-editor in #390
- Add merge group trigger by @sorpaas in #393
- Add EIP-7623 support to
evm1.0 by @manuelmauro in #391 - chore: fix typo by @Forostovec in #394
- Allow generic-array deprecation by @sorpaas in #398
- Support multiple underlying uint256 libraries by @sorpaas in #399
Full Changelog: evm-v1.0.0...evm-v1.1.0
New contributors
- @ozrg made their first contribution in #384
- @GarmashAlex made their first contribution in #386
- @VolodymyrBg made their first contribution in #387
- @MozirDmitriy made their first contribution in #388
- @gap-editor made their first contribution in #390
- @Forostovec made their first contribution in #394