Closed omerfirmak closed 3 weeks ago
using a slice of pointers and allocating on each step of EVM execution puts a lot of unnecessary load on the garbage collector.
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
Has the version in params/version.go been updated?
params/version.go
Does this PR have the breaking-change label?
breaking-change
1. Purpose or design rationale of this PR
using a slice of pointers and allocating on each step of EVM execution puts a lot of unnecessary load on the garbage collector.
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.go
been updated?4. Breaking change label
Does this PR have the
breaking-change
label?