From: "David Rheinsberg" <david@readahead.eu>
To: "Danilo Krummrich" <dakr@kernel.org>
Cc: rust-for-linux@vger.kernel.org,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Uladzislau Rezki" <urezki@gmail.com>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust/alloc: add Vec::into_boxed_slice()
Date: Thu, 26 Mar 2026 13:20:53 +0100 [thread overview]
Message-ID: <061ea42f-bb21-4dc0-853d-fd2391309d56@app.fastmail.com> (raw)
In-Reply-To: <DHCNOY4GFV7B.3VGGZNT3382L0@kernel.org>
Hi
On Thu, Mar 26, 2026, at 11:53 AM, Danilo Krummrich wrote:
> On Thu Mar 26, 2026 at 10:56 AM CET, David Rheinsberg wrote:
>> Add `Vec::into_boxed_slice()` similar to
>> `std::vec::Vec::into_boxed_slice()` [1].
>
> Do you have a user for this?
Yes.
>> + /// Converts the vector into [`Box<[T], A>`].
>> + ///
>> + /// Excess capacity is retained in the allocation, but lost until the box
>> + /// is dropped.
>> + pub fn into_boxed_slice(self) -> Box<[T], A> {
>> + let (buf, len, _cap) = self.into_raw_parts();
>> + let slice = ptr::slice_from_raw_parts_mut(buf, len);
>> +
>> + // SAFETY:
>> + // - `slice` has been allocated with `A`
>> + // - `slice` is suitably aligned
>> + // - `slice` has at least a length of `len`
>> + // - all elements within `slice` are initialized values of `T`
>> + // - `len` does not exceed `isize::MAX`
>> + unsafe { Box::from_raw(slice) }
>
> Box::from_raw() is missing the safety requirement that the allocation made with
> A must have been made for Layout::for_value::<T>(), as this is what we assume in
> the destructor.
Since `slice` is typed, shouldn't this be implied by:
"`slice` has been allocated with `A`"
There is also no mention of it in `From<Box<[T], A>> for Vec<T, A>`. This should have the same requirements, shouldn't it?
I will gladly mention it in v2, though.
> For this function we should call A::realloc() and document that
> into_boxed_slice() may shrink the backing allocation.
Will do.
> Additionally, can you please add a doc-test?
Do you want me to add a functionality test, or do you want me to add an example for documentation purposes? `doc-test` is a bit ambiguous in that regard.
Thanks
David
next prev parent reply other threads:[~2026-03-26 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 9:56 David Rheinsberg
2026-03-26 10:33 ` Alice Ryhl
2026-03-26 10:45 ` David Rheinsberg
2026-03-26 10:55 ` Danilo Krummrich
2026-03-26 10:53 ` Danilo Krummrich
2026-03-26 12:20 ` David Rheinsberg [this message]
2026-03-26 12:40 ` Danilo Krummrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=061ea42f-bb21-4dc0-853d-fd2391309d56@app.fastmail.com \
--to=david@readahead.eu \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=urezki@gmail.com \
--cc=vbabka@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®