-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor!: streamline OpBlockExecutionError
error type to replace a hard-coded BlockExecutionError
#13696
base: main
Are you sure you want to change the base?
Conversation
OpBlockExecutionError
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good under way! removing the hardcoded F: BlockExecutionStrategyFactory<Error = BlockExecutionError>
should allow you to make progress to get it compiling. aware this pr may grow large.
This reverts commit 7bfd8a7.
This should be rebased to resolve all the merge conflicts, it might become simpler as the legacy tree etc have been removed |
Sorry, will have to be rebased or merged again once #13839 is merged, since nightly clippy is broken right now |
That's ok, I don't see it as a breaking change. |
OpBlockExecutionError
OpBlockExecutionError
error type to replace a hard-coded BlockExecutionError
OpBlockExecutionError
error type to replace a hard-coded BlockExecutionError
OpBlockExecutionError
error type to replace a hard-coded BlockExecutionError
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when new trait BlockExecError
(see comment about rename) is implemented for the OpBlockExecutionError
too, then seems like this is possibly getting closed to finish :D
Current issue
Adding a variant and removing the conversion brings complexities everywhere
BlockExecutionError
hard-coded in the associated type. TakesBlockExecutionStrategyFactory
,BatchExecutor
orBlockExecutorProvider
. And the conversion betweenOpBlockExecutionError -> BlockExecutionError
is still required in some parts of the code.Requires opinions from the core devs before taking extra steps to finish this PR.
Link to the issue: #13644
cc: @emhane