rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Benno Lossin" <lossin@kernel.org>
To: "Alice Ryhl" <aliceryhl@google.com>
Cc: "Markus Probst" <markus.probst@posteo.de>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
	"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Uladzislau Rezki" <urezki@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-leds@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] rust: add basic Pin<Vec<T, A>> abstractions
Date: Mon, 13 Oct 2025 11:39:35 +0200	[thread overview]
Message-ID: <DDH3F3QRN81U.2A00K8U33PSKA@kernel.org> (raw)
In-Reply-To: <aOzEz23fWxHZbvdh@google.com>

On Mon Oct 13, 2025 at 11:22 AM CEST, Alice Ryhl wrote:
> On Mon, Oct 13, 2025 at 10:03:19AM +0200, Benno Lossin wrote:
>> And `Vec::pin_init_slice` would have the following signature:
>> 
>>     fn pin_init_slice<T, I, E>(this: Vec<I>, flags: alloc::Flags) -> Result<Pin<Box<[T]>>>
>>     where
>>         I: PinInit<T, E>,
>>         Error: From<E>;
>
> We already have Box::pin_slice().

Oh that's perfect :) I still think that the helper vec function above
would be useful, if we want to use this pattern (collecting initializers
in a vec) more broadly.

---
Cheers,
Benno

  reply	other threads:[~2025-10-13  9:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-12 14:52 [PATCH v4 0/2] rust: leds: add led classdev abstractions Markus Probst
2025-10-12 14:52 ` [PATCH v4 1/2] rust: add basic Pin<Vec<T, A>> abstractions Markus Probst
2025-10-12 16:26   ` Benno Lossin
2025-10-12 16:57     ` Markus Probst
2025-10-12 21:31       ` Benno Lossin
2025-10-12 22:11         ` Markus Probst
2025-10-13  8:03           ` Benno Lossin
2025-10-13  9:22             ` Alice Ryhl
2025-10-13  9:39               ` Benno Lossin [this message]
2025-10-13 13:43             ` Markus Probst
2025-10-13 14:47               ` Benno Lossin
2025-10-14 14:15                 ` Markus Probst
2025-10-12 14:52 ` [PATCH v4 2/2] rust: leds: add basic led classdev abstractions Markus Probst
2025-10-13 18:34   ` Alice Ryhl
2025-10-13 20:11     ` Danilo Krummrich
2025-10-14 14:46       ` Markus Probst
2025-10-15 13:44     ` Markus Probst
2025-10-15 14:52       ` Danilo Krummrich
2025-10-15 15:02         ` Markus Probst
2025-10-15 17:27           ` Danilo Krummrich
2025-10-12 16:27 ` [PATCH v4 0/2] rust: leds: add " 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=DDH3F3QRN81U.2A00K8U33PSKA@kernel.org \
    --to=lossin@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=markus.probst@posteo.de \
    --cc=ojeda@kernel.org \
    --cc=pavel@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;
as well as URLs for NNTP newsgroup(s).