-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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: Support custom allocators (v1.5) #98103
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
r? @m-ou-se (rust-highfive has picked a reviewer for you, use r? to override) |
r? @Amanieu |
@rustbot modify labels: +A-allocators +T-libs-api -T-compiler -T-libs |
@bors r+ |
📌 Commit 1f7023a has been approved by |
BTreeMap: Support custom allocators (v1.5) Related: rust-lang/wg-allocators#7 https://github.com/TimDiekmann/alloc-wg Blocked on: ~~rust-lang#77187~~ ~~rust-lang#78459~~ ~~rust-lang#95036~~ previous: rust-lang#77438
BTreeMap: Support custom allocators (v1.5) Related: rust-lang/wg-allocators#7 https://github.com/TimDiekmann/alloc-wg Blocked on: ~~rust-lang#77187~~ ~~rust-lang#78459~~ ~~rust-lang#95036~~ previous: rust-lang#77438
☀️ Test successful - checks-actions |
Finished benchmarking commit (1b9daa6): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
This introduced an ICE in Miri: #98176. The actual bug is probably somewhere else and just uncovered here. But the strange thing is that the ICE does not need custom allocators to be triggered. |
FWIW that might be related to the performance regressions -- this PR will create |
I guess that this can be fixed by replacing |
It's unavoidable to change all |
I'm already working on that in #98178 -- sorry. |
The alloc library was switched to the 2021 edition in <rust-lang/rust#92068>. However, it did not use any features of the new edition until PR <rust-lang/rust#98103>, which relies on the newer closure capture mechanism. This commit fixes the build on the latest nightlies, which include that PR. Fixes #104
Related:
rust-lang/wg-allocators#7
https://github.com/TimDiekmann/alloc-wg
Blocked on:
#77187#78459#95036previous: #77438