-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Tracking Issue for BTreeMap::merge #152152
Copy link
Copy link
Open
Labels
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-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
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-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Feature gate:
#![feature(btree_merge)]This is a tracking issue for rust-lang/libs-team#739
It adds a method similar to
BTreeMap::appendwith merging twoBTreeMaps inO(n + m)complexity, but allows the user to specify a callback function to handle what the resulting value should be for conflicting keys.Public API
Steps / History
(Remember to update the
S-tracking-*label when checking boxes.)BTreeMap::append_withlibs-team#739BTreeMap::mergeoptimized #152418BTreeMap::merge#153040Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩