Don't re-export items from the traits submodule in the storage module #751
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.
This PR will be redone after #733
The motivation for this PR is to make it so that
Sha256Hasher
andStorageHasher
are only importable in exactly one way outside of thecrate::ledger::storage
module. Currently, these two types are importable directly fromcrate::ledger::storage::traits
but also re-exported incrate::ledger::storage
as well, meaning they are arbitrarily imported throughout the codebase in different ways which can lead to merge conflicts. i.e.namada/shared/src/ledger/storage/mod.rs
Line 27 in 6cbce4a
This PR is currently changing the imports to work like so:
Sha256Hasher
moved fromcrate::ledger::storage::traits
tocrate::ledger::storage
(so now only importable viacrate::ledger::storage
)StorageHasher
is now only importable viacrate::ledger::storage::traits