From: Alice Ryhl <aliceryhl@google.com>
To: Benno Lossin <lossin@kernel.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Fiona Behrens" <me@kloenk.dev>, "Alban Kurti" <kurti@invicto.ai>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rust: pin-init: add `#[bind]` attribute to access previously initialized fields
Date: Wed, 10 Sep 2025 10:17:19 +0000 [thread overview]
Message-ID: <aMFQL-Hq1KvBG5lh@google.com> (raw)
In-Reply-To: <20250910100755.2361281-1-lossin@kernel.org>
On Wed, Sep 10, 2025 at 12:07:53PM +0200, Benno Lossin wrote:
> Assigning a field a value in an initializer macro can be marked with the
> `#[bind]` attribute. Doing so creates a `let` binding with the same
> name. This `let` binding has the type `Pin<&mut T>` if the field is
> structurally pinned or `&mut T` otherwise (where `T` is the type of the
> field).
>
> Signed-off-by: Benno Lossin <lossin@kernel.org>
Is there a reason we can't apply this to all fields and avoid the
attribute?
Do we have a place that might be able to use this?
Alice
next prev parent reply other threads:[~2025-09-10 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 10:07 [PATCH v2] rust: pin-init: add `#[bind]` attribute to access previously initialized fields Benno Lossin
2025-09-10 10:17 ` Alice Ryhl [this message]
2025-09-10 10:35 ` Benno Lossin
2025-09-10 10:40 ` Alice Ryhl
2025-09-10 11:15 ` Danilo Krummrich
2025-09-10 11:52 ` Alice Ryhl
2025-09-10 13:09 ` Danilo Krummrich
2025-09-10 12:19 ` Benno Lossin
2025-09-10 13:55 ` Danilo Krummrich
2025-09-10 14:02 ` Boqun Feng
2025-09-10 14:59 ` Benno Lossin
2025-09-10 15:06 ` Boqun Feng
2025-09-10 15:39 ` Benno Lossin
2025-09-10 15:08 ` 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=aMFQL-Hq1KvBG5lh@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=kurti@invicto.ai \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=me@kloenk.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).