From: "Danilo Krummrich" <dakr@kernel.org>
To: "Benno Lossin" <lossin@kernel.org>
Cc: "Gary Guo" <gary@garyguo.net>, "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>,
"Fiona Behrens" <me@kloenk.dev>,
"Tim Chirananthavat" <theemathas@gmail.com>,
stable@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: pin-init: replace shadowed return token by `unsafe`-to-create token
Date: Wed, 11 Mar 2026 14:01:35 +0100 [thread overview]
Message-ID: <DGZZ0XF0YYGN.1W5UIBXK16HL3@kernel.org> (raw)
In-Reply-To: <20260311105056.1425041-1-lossin@kernel.org>
On Wed Mar 11, 2026 at 11:50 AM CET, Benno Lossin wrote:
> In the face of Type Alias Impl Trait (TAIT) and the next trait solver,
> this solution no longer works [1]. The shadowed struct can be named
> through type inference. In addition, there is an RFC proposing to add
> the feature of path inference to Rust, which would similarly allow [2]
NIT: I'm not sure if the sentence is supposed to end here, at least it misses a
period.
Besides that, is my understanding correct that the changes mentioned above are
targeting a subsequent Rust edition?
next prev parent reply other threads:[~2026-03-11 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 10:50 [PATCH] rust: pin-init: replace shadowed return token by `unsafe`-to-create token Benno Lossin
2026-03-11 12:51 ` Gary Guo
2026-03-11 13:01 ` Danilo Krummrich [this message]
2026-03-11 16:04 ` Alice Ryhl
2026-03-11 16:11 ` Gary Guo
2026-03-11 18:14 ` Benno Lossin
2026-03-11 16:02 ` Alice Ryhl
2026-03-12 7:57 ` Miguel Ojeda
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=DGZZ0XF0YYGN.1W5UIBXK16HL3@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=gary@garyguo.net \
--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=stable@vger.kernel.org \
--cc=theemathas@gmail.com \
--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.