-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 #77438
Conversation
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
☔ The latest upstream changes (presumably #77436) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
41c0200
to
c7237fa
Compare
@rustbot modify labels: +A-allocators +T-libs |
☔ The latest upstream changes (presumably #77470) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
This comment has been minimized.
This comment has been minimized.
cc @Amanieu |
r? @Amanieu |
6d0cfa5
to
78a3633
Compare
☔ The latest upstream changes (presumably #77981) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
BTreeMap: refactor Entry out of map.rs into its own file btree/map.rs is approaching the 3000 line mark, splitting out the entry code buys about 500 lines of headroom. I've created this PR because the changes I've made in rust-lang#77438 will push `map.rs` over the 3000 line limit and cause tidy to complain. I picked `Entry` to factor out because it feels less tightly coupled to the rest of `BTreeMap` than the various iterator implementations. Related: rust-lang#60302
BTreeMap: refactor Entry out of map.rs into its own file btree/map.rs is approaching the 3000 line mark, splitting out the entry code buys about 500 lines of headroom. I've created this PR because the changes I've made in rust-lang#77438 will push `map.rs` over the 3000 line limit and cause tidy to complain. I picked `Entry` to factor out because it feels less tightly coupled to the rest of `BTreeMap` than the various iterator implementations. Related: rust-lang#60302
78a3633
to
da43320
Compare
BTreeMap: refactor Entry out of map.rs into its own file btree/map.rs is approaching the 3000 line mark, splitting out the entry code buys about 500 lines of headroom. I've created this PR because the changes I've made in rust-lang#77438 will push `map.rs` over the 3000 line limit and cause tidy to complain. I picked `Entry` to factor out because it feels less tightly coupled to the rest of `BTreeMap` than the various iterator implementations. Related: rust-lang#60302
☔ The latest upstream changes (presumably #78060) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
da43320
to
cf67d7d
Compare
☔ The latest upstream changes (presumably #77244) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #95702) made this pull request unmergeable. Please resolve the merge conflicts. |
Triage: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about the late review, this looks good modulo the leftover test code. Can you rebase to resolve the conflicts?
@@ -1684,6 +1684,7 @@ impl<'a> Builder<'a> { | |||
rustflags.arg(&format!("-Cllvm-args=-import-instr-limit={}", limit)); | |||
} | |||
} | |||
cargo.env(profile_var("LTO"), "off"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leftover from testing?
What's the status of the PR? I'd like to help with something. |
@TennyZhuang Since the author is not responding, you can take over by forking their code and opening a new PR. |
@exrook Sorry but I really need the feature, I'll take over the PR at the weekend. 🥰 |
Closing this in favour of #98015 |
@TennyZhuang I'm glad to hear you're also looking to use this feature! My apologies for not responding sooner, I've been busy with other things, and when I last attempted a rebase on master back in May I was still hitting box-related ICEs so I've been working on a branch based on top of #95576, though it seems now those ICEs have been fixed in master :). @Dylan-DPC Hi, could this be re-opened? I've put a lot of effort into keeping these changes in sync with master over the past year+ and a half and I'd like to see it through to being merged. :) @Amanieu Thanks for the review! I've rebased on master and removed the leftover test code, so this should be good to go if you have no other comments |
@exrook I’m glad to hear that, and really hope the PR can be merged ASAP. |
GIthub doesn't let me reopen the PR after a force-push/rebase. You'll need to open a new one. |
@exrook I’ve found that it’s possible to reopen the PR, but you have to revert the commits back to the one before closed, and commit them again, sorry. See https://gist.github.com/robertpainsi/2c42c15f1ce6dab03a0675348edd4e2c Feel free to reopen the PR or just create a new one. |
@exrook unfortunately you can't reöpen this. You can submit a new pull request and link this one in the description and we can take it from there |
Thanks everyone! I've opened a new PR at #98103 |
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
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
Moved to #98103
Related:
rust-lang/wg-allocators#7
https://github.com/TimDiekmann/alloc-wg
Blocked on:
#77187#78459#95036