Relax constraint in hash_map::EntryRef insertion methods K: From<&Q> to &Q: Into<K>#611
Merged
Amanieu merged 1 commit intorust-lang:masterfrom Apr 5, 2025
Merged
Relax constraint in hash_map::EntryRef insertion methods K: From<&Q> to &Q: Into<K>#611Amanieu merged 1 commit intorust-lang:masterfrom
Amanieu merged 1 commit intorust-lang:masterfrom
Conversation
…to &Q: Into<K> Currently `EntryRef::or_insert*` methods have constraint `K: From<&Q>` which is required to construct "owned" key from "borrowed" key during insertion operation. Rust documentation recommends not to use `From` as trait constraint, and instead prefer to use reversed `Into` trait constraint: https://doc.rust-lang.org/std/convert/trait.From.html > Prefer using Into over using From when specifying trait bounds on a generic > function. This way, types that directly implement Into can be used as arguments as well. Changing constraint `K: From<&Q>` to `&Q: Into<K>` extends support of insert operation to additional cases where `K` does not implement trait `From<&Q>`, but `&Q` does implement trait `Into<K>`. **API compatibility**: `&Q: Into<K>` is a strict superset of `K: From<&Q>` (because of blanket implementation https://doc.rust-lang.org/std/convert/trait.Into.html#impl-Into%3CU%3E-for-T), so this change does not break existing hashbrown API compatibility; all existing code will work with new trait constraints.
Amanieu
approved these changes
Apr 5, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently
EntryRef::or_insert*methods have constraintK: From<&Q>which is required to construct "owned" key from "borrowed" key during insertion operation.Rust documentation recommends not to use
Fromas trait constraint, and instead prefer to use reversedIntotrait constraint:https://doc.rust-lang.org/std/convert/trait.From.html
Changing constraint
K: From<&Q>to&Q: Into<K>extends support of insert operation to additional cases whereKdoes not implement traitFrom<&Q>, but&Qdoes implement traitInto<K>.API compatibility:
&Q: Into<K>is a strict superset ofK: From<&Q>(because of blanket implementation https://doc.rust-lang.org/std/convert/trait.Into.html#impl-Into%3CU%3E-for-T), so this change does not break existing hashbrown API compatibility; all existing code will work with new trait constraints.