Fixing ManualKey<0> to act properly
#1670
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…bility of really using the zero storage key. This fix allows using the zero manual key that overrides the auto-generated key.
xgreenx
requested review from
cmichi,
ascjones,
HCastano and
SkymanOne
as code owners
xgreenx
commented
Feb 21, 2023
| <ResolverKey<ManualKey<456>, ManualKey<123>> as StorageKey>::KEY, | ||
| 456 | ||
| ); | ||
| assert_eq!( |
There was a problem hiding this comment.
Without the fix, it would fail with the 123 storage key=)
|
Thanks for the PR, @xgreenx! Can you add a changelog entry to the |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously the
ManualKey<0>acted as anAutoKeywithout the possibility of really using the zero storage key. This fix allows using the zero manual key that overrides the auto-generated key.