-
-
Notifications
You must be signed in to change notification settings - Fork 17.8k
Tracking Issue for map_try_insert #82766
Copy link
Copy link
Open
Labels
A-collectionsArea: `std::collections`Area: `std::collections`C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Description
Activity
Metadata
Metadata
Assignees
Labels
A-collectionsArea: `std::collections`Area: `std::collections`C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
View all comments
Feature gate:
#![feature(map_try_insert)]This is a tracking issue for
BTreeMap::try_insertandHashMap::try_insert.Unlike
.insert(),.try_insert()does not overwrite existing values, and has a meaningful error type with more context. See #82764Public API
Steps / History
Unresolved Questions
OccupiedErrorimplement Error (and Display)? They are not especially useful with the captured lifetime. Add {BTreeMap,HashMap}::try_insert #82764 (comment)OccupiedErrorhave public fields, or accessors? Add {BTreeMap,HashMap}::try_insert #82764 (comment)try_might imply it returns anErrwhen allocating fails, which is not the case. Maybe rename it toinsert_newor something?key: Kargument into theOccupiedError?