Expose the key of Entry variants for HashMap and BTreeMap. #32248
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @aturon (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
| @@ -1465,6 +1465,13 @@ impl<'a, K: Ord, V> Entry<'a, K, V> { | |||
| } | |||
|
|
|||
| impl<'a, K: Ord, V> VacantEntry<'a, K, V> { | |||
| /// Gets a reference to the key that would be used when inserting a value | |||
| /// through the VacantEntry. | |||
| #[unstable(feature = "map_entry_keys", issue = "1541")] | |||
There was a problem hiding this comment.
I think this will have to reference an issue in the rust-lang/rust repo, not rust-lang/rfcs.
|
This PR pushes the API in the right direction. See also issue 1533: Keyless Entry. |
Expose the key of Entry variants for HashMap and BTreeMap. This PR addresses [issue 1541](rust-lang/rfcs#1541) by exposing the key of `HashMap` and `BTreeMap` entry variants. Basic tests are provided.
This PR addresses issue 1541 by exposing the key of
HashMapandBTreeMapentry variants. Basic tests are provided.