add BinaryHeap::try_reserve and BinaryHeap::try_reserve_exact#91529
add BinaryHeap::try_reserve and BinaryHeap::try_reserve_exact#91529bors merged 2 commits intorust-lang:masterfrom
Conversation
|
r? @yaahc (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
35e8e1c to
a434385
Compare
|
@rustbot label: +T-libs-api |
|
I think this PR should be part of #48043 |
But the feature was stabilized in 1.57.0, we need another feature gate. |
…scottmcm Suggest try_reserve in try_reserve_exact During developing rust-lang#91529 , I found that `try_reserve_exact` suggests `reserve` for further insertions. I think it's a mistake by copy&paste, `try_reserve` is better here.
…scottmcm Suggest try_reserve in try_reserve_exact During developing rust-lang#91529 , I found that `try_reserve_exact` suggests `reserve` for further insertions. I think it's a mistake by copy&paste, `try_reserve` is better here.
…scottmcm Suggest try_reserve in try_reserve_exact During developing rust-lang#91529 , I found that `try_reserve_exact` suggests `reserve` for further insertions. I think it's a mistake by copy&paste, `try_reserve` is better here.
…scottmcm Suggest try_reserve in try_reserve_exact During developing rust-lang#91529 , I found that `try_reserve_exact` suggests `reserve` for further insertions. I think it's a mistake by copy&paste, `try_reserve` is better here.
|
lgtm, just needs a tracking issue. I agree that you should setup a new one since the related feature has already merged. |
Is it necessary for me to create an RFC other than for tracking issues? |
No, not in this case. |
Signed-off-by: TennyZhuang <zty0826@gmail.com>
a434385 to
d0f8793
Compare
|
Looks great, thank you very much! @bors r+ |
|
📌 Commit 2235af1 has been approved by |
…, r=yaahc add BinaryHeap::try_reserve and BinaryHeap::try_reserve_exact `try_reserve` of many collections were stablized in rust-lang#87993 in 1.57.0. Add `try_reserve` for the rest collections such as `BinaryHeap` should be not controversial.
…askrgr Rollup of 7 pull requests Successful merges: - rust-lang#91529 (add BinaryHeap::try_reserve and BinaryHeap::try_reserve_exact) - rust-lang#91820 (Suggest to specify a target triple when lang item is missing) - rust-lang#91851 (Make `MaybeUninit::zeroed` `const`) - rust-lang#91875 (Use try_normalize_erasing_regions in RevealAllVisitor) - rust-lang#91887 (Remove `in_band_lifetimes` from `rustc_const_eval`) - rust-lang#91892 (Fix HashStable implementation on InferTy) - rust-lang#91893 (Remove `in_band_lifetimes` from `rustc_hir`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
try_reserveof many collections were stablized in #87993 in 1.57.0. Addtry_reservefor the rest collections such asBinaryHeapshould be not controversial.