Repository navigation
Tracking Issue for const_collections_with_hasher #102575
Description
Activity
- addedC-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-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]
on Oct 2, 2022 What blocks this from stabilization? Can I do something to move it forward?
@GoldsteinE: see https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Main questions for stabilization are do we want to add the constraint that an empty hashmap can be const constructed (ie doesn't alloc and more). This is true for the current hashbrown design, but might not be true for other alternatives. I'm not framiliar enough with hashmap design to say.
This is fairly straightforward, we are essentially guaranteeing that a newly created
HashMapdoes not allocate any memory.@rfcbot fcp merge
Team member @Amanieu has proposed to merge this. The next step is review by the rest of the tagged team members:
No concerns currently listed.
Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!
See this document for info about what commands tagged team members can give me.
- addedproposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.This issue / PR is in PFCP or FCP with a disposition to merge it.final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.In the final comment period and will be merged soon unless new substantive objections are raised.and removedproposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
on Aug 3, 2023 🔔 This is now entering its final comment period, as per the review above. 🔔
- addedfinished-final-comment-periodThe final comment period is finished for this PR / Issue.The final comment period is finished for this PR / Issue.to-announceAnnounce this issue on triage meetingAnnounce this issue on triage meetingand removedfinal-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.In the final comment period and will be merged soon unless new substantive objections are raised.
on Aug 13, 2023 15 remaining items
- added a commit that references this issue
on Nov 3, 2024 The PR that should enable us to safely expose
const fnfrom hashbrown is up now: #132541.(That's just the infrastructure for this, once it lands, a bit of wiring-up needs to happen in hashbrown.)
Reacted by KisaragiCc @rust-lang/wg-const-eval
- added a commit that references this issue
on Nov 30, 2024 - added a commit that references this issue
on Dec 3, 2024 - added a commit that references this issue
on Dec 4, 2024
Feature gate:
#![feature(const_collections_with_hasher)]This is a tracking issue for making
HashMap::with_hasherandHashSet::with_hasherconst.Public API
Steps / History
Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩