refactor: rename BundleStateWithReceipts to BlockExecutionOutcome#8730
refactor: rename BundleStateWithReceipts to BlockExecutionOutcome#8730mattsse merged 10 commits intoparadigmxyz:mainfrom
BundleStateWithReceipts to BlockExecutionOutcome#8730Conversation
mattsse
left a comment
There was a problem hiding this comment.
hmm, this is slightly more nuanced because a ton of variables still refer to this as state and other types also refer to this as state.
I very much prefer this new name because it's accurate.
but this clashes with how we refer to it, referring to this as state is even more confusing...
not sure how to proceed...
crates/blockchain-tree/src/bundle.rs
Outdated
|
|
||
| impl<'a> BundleStateDataProvider for BundleStateDataRef<'a> { | ||
| fn state(&self) -> &BundleStateWithReceipts { | ||
| fn state(&self) -> &BlockExecutionOutcome { |
There was a problem hiding this comment.
hmm, while naming is an improvement, this does not fit if we keep using it like this.
There was a problem hiding this comment.
Yes I thought we were saving it for another PR as there were a lot of changes to make but it's true that it doesn't make much sense to merge like that.
So I tried changing the names around BlockExecutionOutcome for overall consistency, hope I didn't forget any.
Let me know what you think about this
mattsse
left a comment
There was a problem hiding this comment.
I like this a lot more than Bundlestate,
after looking at this, I would even consider dropping the Block prefix and just do ExecutionOutput this way it's not tied to Block because it could this can represent multiple blocks.
but I'd like more feedback here @Rjected @gakonst @shekhirin @rkrasiuk @rakita
|
|
I like |
|
|
|
ExecutionOutput it is then |
|
actually, can we roll this back to |
ee30a63 to
1bd67d3
Compare
This PR:
BundleStateWithReceiptstoBlockExecutionOutcomewith_receiptsandwith_requestsShould close #8727.