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
{{ message }}
This repository has been archived by the owner on Jan 9, 2024. It is now read-only.
Unit tests for TraceCallExecutor should be refactored to improve readability and semantics:
add constructor in EVMExecutor with silkworm::State as input parameter instead of core::rawdb::DatabaseReader
add constructor in TraceCallExecutor with silkworm::State and EVMExecutor as input parameters instead of core::rawdb::DatabaseReader or change TraceCallExecutor::execute
if possible, refactor EVMExecutor and TraceCallExecutor to avoid templates
mock silkworm::State using Gmock
refactor unit tests
rename TraceCallExecutor as TraceExecutor
The text was updated successfully, but these errors were encountered:
Unit tests for
TraceCallExecutor
should be refactored to improve readability and semantics:EVMExecutor
withsilkworm::State
as input parameter instead ofcore::rawdb::DatabaseReader
TraceCallExecutor
withsilkworm::State
andEVMExecutor
as input parameters instead ofcore::rawdb::DatabaseReader
or changeTraceCallExecutor::execute
EVMExecutor
andTraceCallExecutor
to avoid templatessilkworm::State
using GmockTraceCallExecutor
asTraceExecutor
The text was updated successfully, but these errors were encountered: