-
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
Stablize const_binary_heap_constructor
#125211
Conversation
const_binary_heap_constructor
const_binary_heap_constructor
@rustbot label -T-libs +T-libs-api r? libs-api |
Has FCP been completed anywhere? I don't expect this to be controversial given all similar constructors are |
No FCP yet. Should I do it in a new issue? Or just do it in #112353? |
That issue is preferable to this PR, as people would already be subscribed there. |
@rustbot claim
|
Could not assign reviewer from: |
@bors r=jhpratt,dtolnay |
…,dtolnay Stablize `const_binary_heap_constructor` This pr aims to stablize `const_binary_heap_constructor`. `BinaryHeap::new` is able to be stablized, but `BinaryHeap::new_in` is not. Because the latter depends on `Vec::new_in` which is unstable. The `const_binary_heap_constructor` feature contains the two functions, and I want to split this feature now. This pr creates `const_binary_heap_new_in` feature for `BinaryHeap::new_in` and stablizes `const_binary_heap_constructor` (now this original feature only contains one function).
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
Looks like @bors d+ |
… `const_binary_heap_new_in` for `BinaryHeap::new_in`
ef23a5b
to
7cee7c6
Compare
@bors r=jhpratt |
@Coekjan: 🔑 Insufficient privileges: Not in reviewers |
@bors r+ |
Stablize `const_binary_heap_constructor` This pr aims to stablize `const_binary_heap_constructor`. `BinaryHeap::new` is able to be stablized, but `BinaryHeap::new_in` is not. Because the latter depends on `Vec::new_in` which is unstable. The `const_binary_heap_constructor` feature contains the two functions, and I want to split this feature now. This pr creates `const_binary_heap_new_in` feature for `BinaryHeap::new_in` and stablizes `const_binary_heap_constructor` (now this original feature only contains one function).
Stablize `const_binary_heap_constructor` This pr aims to stablize `const_binary_heap_constructor`. `BinaryHeap::new` is able to be stablized, but `BinaryHeap::new_in` is not. Because the latter depends on `Vec::new_in` which is unstable. The `const_binary_heap_constructor` feature contains the two functions, and I want to split this feature now. This pr creates `const_binary_heap_new_in` feature for `BinaryHeap::new_in` and stablizes `const_binary_heap_constructor` (now this original feature only contains one function).
Stablize `const_binary_heap_constructor` This pr aims to stablize `const_binary_heap_constructor`. `BinaryHeap::new` is able to be stablized, but `BinaryHeap::new_in` is not. Because the latter depends on `Vec::new_in` which is unstable. The `const_binary_heap_constructor` feature contains the two functions, and I want to split this feature now. This pr creates `const_binary_heap_new_in` feature for `BinaryHeap::new_in` and stablizes `const_binary_heap_constructor` (now this original feature only contains one function).
Rollup of 3 pull requests Successful merges: - rust-lang#125211 (Stablize `const_binary_heap_constructor`) - rust-lang#125683 (Rewrite `suspicious-library`, `resolve-rename` and `incr-prev-body-beyond-eof` `run-make` tests in `rmake.rs` format) - rust-lang#125822 (Refactor `--print=check-cfg` test) r? `@ghost` `@rustbot` modify labels: rollup
Ah, okay. I went by https://bors.tech/documentation, but I also know that Rust uses its own fork. Looking at https://bors.rust-lang.org, it seems you're correct. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (466be51): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary -0.8%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 666.776s -> 668.037s (0.19%) |
This pr aims to stablize
const_binary_heap_constructor
.BinaryHeap::new
is able to be stablized, butBinaryHeap::new_in
is not. Because the latter depends onVec::new_in
which is unstable.The
const_binary_heap_constructor
feature contains the two functions, and I want to split this feature now. This pr createsconst_binary_heap_new_in
feature forBinaryHeap::new_in
and stablizesconst_binary_heap_constructor
(now this original feature only contains one function).