hash_map::OccupiedEntry::remove_entry #20601
Closed
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.
remove_entry
is like toremove
, but returns both key and value.Sometimes key needs to be recovered, for example, when lookup key
is different from storage key.
P. S.
HashSet::remove(..)
is stable now, so it can't be changed to return contained value. What do you think about having another operation likeremove_value
. I don't need it personally, but it should probably exist for consistency and flexibility.P. P. S. I need
remove_entry
operation to implement LinkedHashSet and LinkedHashMap.