Make StorageTransactionCache clonable if type parameters permit #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We may need to be able to clone the associated
RuntimeApi
instance while cloning the block builder used to propose a block in order to be able to run the pseudo-inherent at the end of a block with a timeout in a separate thread on top of the overlay changes made by the extrinsics in this block, while keeping the old block builder intact in case we need to fall back to it if the timeout expires.The
RuntimeApi
includes a reference to thesp_state_machine::StorageTransactionCache
which doesn't implementClone
by default due to its dependent types, but in the real node all the type parameters involved are clonable.