-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Regenesis support #1413
Regenesis support #1413
Conversation
The Cargo.lock file should not be deleted. It is important for binary distribution stability and ci caching. |
} | ||
|
||
#[derive(Clone, Debug)] | ||
pub struct StateImporter<T> { |
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.
Would it be possible to specify what kind of state, rather than just general StateImporter
? Like ChainState
or whatever is most appropriate.
} | ||
} | ||
|
||
struct InMemorySource { |
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.
Did you consider, instead of abstracting along the Read
and Write
trait, providing some domain specific trait, e.g. ChainStateSource
or something along those lines?
Then instead of injecting this fake file construct, you could have an InMemoryChainStateSource
and a FileSystemChainStateSource
, which would allow you define these things in terms of domain specific actions instead of implementation specific actions:
read_chain_state
vs read
.
Interested to hear your thoughts :)
We've split it into several smaller PRs |
Closes #1450
Remaining tasks: