diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2021-03-30 00:32:18 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-30 00:32:18 +0200 |
| commit | 2843baaeb6e20c494b3b938b4d4024ead7bbdd1b (patch) | |
| tree | 903506aa3d82a267877caae41513a1bf19ec9238 /src/test/ui/thinlto | |
| parent | 48691ea6e639640f110b43e33d4aba1f07e7415c (diff) | |
| parent | 595f3f25fcc9e11598eb0de2b8bb01022386147c (diff) | |
| download | rust-2843baaeb6e20c494b3b938b4d4024ead7bbdd1b.tar.gz rust-2843baaeb6e20c494b3b938b4d4024ead7bbdd1b.zip | |
Rollup merge of #82331 - frol:feat/std-binary-heap-as-slice, r=Amanieu
alloc: Added `as_slice` method to `BinaryHeap` collection I initially asked about whether it is useful addition on https://internals.rust-lang.org/t/should-i-add-as-slice-method-to-binaryheap/13816, and it seems there were no objections, so went ahead with this PR. > There is [`BinaryHeap::into_vec`](https://doc.rust-lang.org/std/collections/struct.BinaryHeap.html#method.into_vec), but it consumes the value. I wonder if there is API design limitation that should be taken into account. Implementation-wise, the inner buffer is just a Vec, so it is trivial to expose as_slice from it. Please, guide me through if I need to add tests or something else. UPD: Tracking issue #83659
Diffstat (limited to 'src/test/ui/thinlto')
0 files changed, 0 insertions, 0 deletions
