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
Currently const generic is defined as an Enum that is used as generic on the functions. This becomes problematic if we want to add some new features and enable just one of them.
Presently on optimism use case where they want to have the hardfork in the middle of existing ones it becomes impossible to define outside of evm and they need to feature gate the new Spec enum with their own.
The main problem is that the Present spec id is considered as a number and assumption is that everything less than this is activated, the idea is to have flag per hardfork and allow granular control of what is enabled. This would additionally allow defining custom hardfork that can be activated on any time.
An additional benefit is enabling future EIPs which would allow testing on isolation, when that EIP get merged into hardfork all flags for it would be merged into one.
The text was updated successfully, but these errors were encountered:
Currently const generic is defined as an Enum that is used as generic on the functions. This becomes problematic if we want to add some new features and enable just one of them.
Presently on optimism use case where they want to have the hardfork in the middle of existing ones it becomes impossible to define outside of evm and they need to feature gate the new Spec enum with their own.
The main problem is that the Present spec id is considered as a number and assumption is that everything less than this is activated, the idea is to have flag per hardfork and allow granular control of what is enabled. This would additionally allow defining custom hardfork that can be activated on any time.
An additional benefit is enabling future EIPs which would allow testing on isolation, when that EIP get merged into hardfork all flags for it would be merged into one.
The text was updated successfully, but these errors were encountered: