-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BTreeMap::new_in should be const #118
Comments
Sounds good! Feel free to submit a PR and assign it to me for review. |
Kritzefitz
added a commit
to Kritzefitz/rust
that referenced
this issue
Oct 9, 2023
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Oct 10, 2023
…manieu Mark `new_in` as `const` for BTree collections Discussed in and closes rust-lang/wg-allocators#118
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Oct 10, 2023
…manieu Mark `new_in` as `const` for BTree collections Discussed in and closes rust-lang/wg-allocators#118
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 10, 2023
Rollup merge of rust-lang#116559 - Kritzefitz:btree-new-in-const, r=Amanieu Mark `new_in` as `const` for BTree collections Discussed in and closes rust-lang/wg-allocators#118
If I'm not mistaken, the merged PR fixes this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The title basically already says it all.
alloc::collections::btree_map::BTreeMap::new_in
is currently not marked asconst
, even though there doesn't seem to be a good reason why it shouldn't be.The text was updated successfully, but these errors were encountered: