From: "Benno Lossin" <lossin@kernel.org>
To: "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>
Cc: "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>,
"Alice Ryhl" <aliceryhl@google.com>,
"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: Sun, 12 Oct 2025 18:26:54 +0200 [thread overview]
Message-ID: <DDGHGF4XOJQG.2MVGBMPK0KUQE@kernel.org> (raw)
In-Reply-To: <20251012145221.172116-2-markus.probst@posteo.de>
On Sun Oct 12, 2025 at 4:52 PM CEST, Markus Probst wrote:
> @@ -109,6 +111,21 @@ pub struct Vec<T, A: Allocator> {
> _p: PhantomData<A>,
> }
>
> +/// Extension for Pin<Vec<T, A>>
> +pub trait PinnedVecExt<T> {
Why is this an extension trait? Couldn't we directly implement this on
`Vec<T>` with `self: Pin<&mut Self>`?
---
Cheers,
Benno
> + /// Pin-initializes P and appends it to the back of the [`Vec`] instance without reallocating.
> + fn push_pin_init<E: From<PushError<P>>, P: PinInit<T, E>>(&mut self, init: P) -> Result<(), E>;
> +
> + /// Shortens the vector, setting the length to `len` and drops the removed values.
> + /// If `len` is greater than or equal to the current length, this does nothing.
> + ///
> + /// This has no effect on the capacity and will not allocate.
> + fn truncate(&mut self, len: usize);
> +
> + /// Removes the last element from a vector and drops it returning true, or false if it is empty.
> + fn pop(&mut self) -> bool;
> +}
> +
> /// Type alias for [`Vec`] with a [`Kmalloc`] allocator.
> ///
> /// # Examples
next prev parent reply other threads:[~2025-10-12 16:27 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 [this message]
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
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=DDGHGF4XOJQG.2MVGBMPK0KUQE@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).