From: "Benno Lossin" <lossin@kernel.org>
To: "Danilo Krummrich" <dakr@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>
Cc: "Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Uladzislau Rezki" <urezki@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: alloc: allow different error types in `KBox::pin_slice`
Date: Sat, 14 Feb 2026 15:40:21 +0100 [thread overview]
Message-ID: <DGERGXTEJ2B2.24F7OWLIZZAK7@kernel.org> (raw)
In-Reply-To: <DGEQZHTOW6FC.2SWNBWY9XE3LD@kernel.org>
On Sat Feb 14, 2026 at 3:17 PM CET, Danilo Krummrich wrote:
> On Sat Feb 14, 2026 at 2:28 PM CET, Andreas Hindborg wrote:
>> @@ -333,24 +333,31 @@ pub fn pin(x: T, flags: Flags) -> Result<Pin<Box<T, A>>, AllocError>
>> /// assert_eq!(s[3].d.lock().a, 20);
>> /// # Ok::<(), Error>(())
>> /// ```
>> - pub fn pin_slice<Func, Item, E>(
>> + pub fn pin_slice<Func, Item, E, E2>(
>> mut init: Func,
>> len: usize,
>> flags: Flags,
>> ) -> Result<Pin<Box<[T], A>>, E>
>> where
>> Func: FnMut(usize) -> Item,
>> - Item: PinInit<T, E>,
>> - E: From<AllocError>,
>
> I think we should keep this bound and just add:
The `Into` trait bounds are the idiomatic ones for functions consuming
things. See https://doc.rust-lang.org/std/convert/trait.Into.html:
Prefer using Into over From when specifying trait bounds on a
generic function to ensure that types that only implement Into can
be used as well.
I should've said something to Andreas, since he created the commit
message (but this patch has left my L3 cache).
Cheers,
Benno
> E: From<E2>,
>
>> + Item: PinInit<T, E2>,
>> + AllocError: Into<E>,
>> + E2: Into<E>,
>> {
>> - let mut buffer = super::Vec::<T, A>::with_capacity(len, flags)?;
>> + let mut buffer = match super::Vec::<T, A>::with_capacity(len, flags) {
>> + Ok(buffer) => buffer,
>> + Err(err) => return Err(err.into()),
>> + };
>
> This...
>
>> for i in 0..len {
>> let ptr = buffer.spare_capacity_mut().as_mut_ptr().cast();
>> // SAFETY:
>> // - `ptr` is a valid pointer to uninitialized memory.
>> // - `ptr` is not used if an error is returned.
>> // - `ptr` won't be moved until it is dropped, i.e. it is pinned.
>> - unsafe { init(i).__pinned_init(ptr)? };
>> + match unsafe { init(i).__pinned_init(ptr) } {
>> + Ok(()) => (),
>> + Err(err) => return Err(err.into()),
>> + }
>
> ...and this match becomes unnecessary then.
next prev parent reply other threads:[~2026-02-14 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 13:28 [PATCH] rust: alloc: allow different error types in `KBox::pin_slice` Andreas Hindborg
2026-02-14 13:37 ` Andreas Hindborg
2026-02-14 14:17 ` Danilo Krummrich
2026-02-14 14:40 ` Benno Lossin [this message]
2026-02-14 14:56 ` Danilo Krummrich
2026-02-15 23:29 ` Benno Lossin
2026-02-16 8:48 ` Alice Ryhl
2026-02-16 9:37 ` Danilo Krummrich
2026-02-27 14:38 ` Gary Guo
2026-02-14 14:37 ` Benno Lossin
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=DGERGXTEJ2B2.24F7OWLIZZAK7@kernel.org \
--to=lossin@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
/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