All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benno Lossin" <lossin@kernel.org>
To: "Boqun Feng" <boqun.feng@gmail.com>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@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>,
	"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 16:59:11 +0200	[thread overview]
Message-ID: <DCP7JTWPA4QS.9PTE12UVZFDC@kernel.org> (raw)
In-Reply-To: <aMGE64_J5R8U_rk5@tardis-2.local>

On Wed Sep 10, 2025 at 4:02 PM CEST, Boqun Feng wrote:
> On Wed, Sep 10, 2025 at 02:19:00PM +0200, Benno Lossin wrote:
>> On Wed Sep 10, 2025 at 12:40 PM CEST, Alice Ryhl wrote:
>> > On Wed, Sep 10, 2025 at 12:36 PM Benno Lossin <lossin@kernel.org> wrote:
>> >>
>> >> On Wed Sep 10, 2025 at 12:17 PM CEST, Alice Ryhl wrote:
>> >> > 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?
>> >>
>> >> Adding the attribute was due to Boqun's concern on v1 [1]. I think it
>> >> might be surprising too, but I'm also happy with no attribute.
>> >>
>> >> [1]: https://lore.kernel.org/all/aLshd0_C-1rh3FAg@tardis-2.local
>> >
>> > IMO the ideal is if it works without an attribute. Perhaps trying that
>> > in the kernel is a reasonable experiment to find out whether that's
>> > reasonable to do for the general language feature?
>> 
>> @Boqun what is your opinion on this?
>> 
>
> If we plan to make the in-place initializer language feature behave
> similar, as I asked here [1], then dropping `#[bind]` seems good to me.

I don't think we can promise how that language feature is going to look
like. It will definitely support accessing already initialized fields,
but in what form remains to be seen.

---
Cheers,
Benno

> [1]: https://lore.kernel.org/rust-for-linux/aLshd0_C-1rh3FAg@tardis-2.local/
>
> Thanks!
>
> Regards,
> Boqun
>
>> I'm open to take v2 or v1, whatever you guys prefer.
>> 
>> ---
>> Cheers,
>> Benno


  reply	other threads:[~2025-09-10 14:59 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
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 [this message]
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=DCP7JTWPA4QS.9PTE12UVZFDC@kernel.org \
    --to=lossin@kernel.org \
    --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=kurti@invicto.ai \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.