All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Gary Guo" <gary@garyguo.net>, "Benno Lossin" <lossin@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Onur Özkan" <work@onurozkan.dev>
Cc: <linux-kernel@vger.kernel.org>, <rust-for-linux@vger.kernel.org>,
	"Mohamad Alsadhan" <mo@sdhn.cc>
Subject: Re: [PATCH 0/4] rust: pin-init: support tuple structs
Date: Mon, 14 Sep 2026 12:33:32 +0100	[thread overview]
Message-ID: <DLF09DXIHB6X.1U9MWU2V1T29W@garyguo.net> (raw)
In-Reply-To: <20260904-tuple-struct-v1-0-72c50bd037fd@garyguo.net>

On Fri Sep 4, 2026 at 3:12 PM BST, Gary Guo wrote:
> This is a long requested feature to support tuple structs. There are a few
> cases that structs have to be converted to become normal structs so
> pin-init can be used.
>
> This series add tuple struct support as you'd expect to work. A caveat is
> that pinned initialization syntax (`<-`) only works with struct expression
> initializers. So
>
>     #[pin_data]
>     struct Foo<T>(#[pin] T, usize)
>
> would need
>
>     pin_init!(Foo {
>         0 <- expr,
>         1: 0
>     })
>
> This is to avoid introducing new syntax.
>
> The upstream pull request for this series is
> https://github.com/Rust-for-Linux/pin-init/pull/155
>
> Signed-off-by: Gary Guo <gary@garyguo.net>
> ---
> Gary Guo (1):
>       rust: pin-init: internal: extract utility code to new module
>
> Mohamad Alsadhan (3):
>       rust: pin-init: internal: pin_data: support tuple struct projections
>       rust: pin-init: internal: init: support tuple structs in `[pin_]init!`
>       rust: pin-init: internal: init: support tuple struct constructor syntax

Applied to pin-init-next.

Best,
Gary

>
>  rust/pin-init/internal/src/init.rs     | 494 ++++++++++++++++++++++++++++-----
>  rust/pin-init/internal/src/lib.rs      |  12 +-
>  rust/pin-init/internal/src/pin_data.rs | 129 ++++++---
>  rust/pin-init/internal/src/util.rs     |  54 ++++
>  rust/pin-init/src/lib.rs               |  71 ++++-
>  5 files changed, 638 insertions(+), 122 deletions(-)
> ---
> base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
> change-id: 20260904-tuple-struct-5b5b6e6a75f9
>
> Best regards,
> --  
> Gary Guo <gary@garyguo.net>



      parent reply	other threads:[~2026-09-14 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 14:12 [PATCH 0/4] rust: pin-init: support tuple structs Gary Guo
2026-09-04 14:12 ` [PATCH 1/4] rust: pin-init: internal: extract utility code to new module Gary Guo
2026-09-04 14:12 ` [PATCH 2/4] rust: pin-init: internal: pin_data: support tuple struct projections Gary Guo
2026-09-04 14:12 ` [PATCH 3/4] rust: pin-init: internal: init: support tuple structs in `[pin_]init!` Gary Guo
2026-09-04 14:12 ` [PATCH 4/4] rust: pin-init: internal: init: support tuple struct constructor syntax Gary Guo
2026-09-14 11:33 ` Gary Guo [this message]

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=DLF09DXIHB6X.1U9MWU2V1T29W@garyguo.net \
    --to=gary@garyguo.net \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=mo@sdhn.cc \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    /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.