diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-01-19 08:15:05 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-19 08:15:05 +0100 |
| commit | 7219bd22ed2df5c94250248d74a2d8549023b72a (patch) | |
| tree | 5e75cb1cd1cc9d6629db7a380f6278fd112af3cf /compiler/rustc_codegen_gcc/tools/generate_intrinsics.py | |
| parent | 332f8f73ea581fd5cb2ee94c1b9ae31dd61d4d67 (diff) | |
| parent | 35a9fc3472b232b924b843c468399ca44320a55d (diff) | |
| download | rust-7219bd22ed2df5c94250248d74a2d8549023b72a.tar.gz rust-7219bd22ed2df5c94250248d74a2d8549023b72a.zip | |
Rollup merge of #120110 - invpt:patch-1, r=the8472
Update documentation for Vec::into_boxed_slice to be more clear about excess capacity Currently, the documentation for Vec::into_boxed_slice says that "if the vector has excess capacity, its items will be moved into a newly-allocated buffer with exactly the right capacity." This is misleading, as copies do not necessarily occur, depending on if the allocator supports in-place shrinking. I copied some of the wording from shrink_to_fit, though it could potentially still be worded better than this.
Diffstat (limited to 'compiler/rustc_codegen_gcc/tools/generate_intrinsics.py')
0 files changed, 0 insertions, 0 deletions