Fix ownership issue with KeyOrValue #786
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
A Key<T> does not always return a value, T; it can return a borrowed value. This is only really exercised by String, which we return by reference. In a situation like this, we cannot have From<T> for KeyOrValue<T> as well as From<Key<T>> for KeyOrValue<T>, because the owned type may be different then the type used by the key. This is fixed by explicitly implementing From in terms of or ValueType trait, so that we can reference the owned type directly.
cmyr
force-pushed
the
fixup-key-or-value
branch
from
4b85e3e to
b3ab0af
Compare
futurepaul
approved these changes
Mar 31, 2020
There was a problem hiding this comment.
Tests pass, styled_text runs, and the associated type means the rust compiler can guard against mis-use. Thanks for the zulip walkthrough!
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.
A
Key<T>does not always return a value,T; it can return a borrowedvalue. This is only really exercised by String, which we return by reference.
In a situation like this, we cannot have
From<T>forKeyOrValue<T>as well asFrom<Key<T>>forKeyOrValue<T>, because the owned type may be different then the type used by the key.This is fixed by explicitly implementing
Fromin terms of ourValueTypetrait, so that we can reference the owned type directly.This should unblock #785.
cc @futurepaul, who might be curious about this.