From: Danilo Krummrich <dakr@kernel.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Vitaly Wool" <vitaly.wool@konsulko.se>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Bjorn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Onur Özkan" <work@onurozkan.dev>
Subject: Re: [PATCH v2] rust: rbtree: add immutable cursor
Date: Wed, 10 Sep 2025 21:42:21 +0200 [thread overview]
Message-ID: <0d8b8918-fe90-4eca-989a-d24cf95c1dd5@kernel.org> (raw)
In-Reply-To: <e49f9e6c-69ee-4ec1-bcc8-3a60fda9a7be@nvidia.com>
On 9/10/25 9:40 PM, John Hubbard wrote:
> It leaves unanswered, the question of whether (and how) to use something
> like the &raw feature, which requires Rust 1.82.0, given that the
> stated min Rust version is 1.78.
The trick is that we have the option to enable unstable features that (in the
exact same way) have been stabilized in recent versions, without facing any
downsides.
next prev parent reply other threads:[~2025-09-10 19:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 14:02 [PATCH v2] rust: rbtree: add immutable cursor Vitaly Wool
2025-09-08 8:47 ` Alice Ryhl
2025-09-08 9:06 ` Danilo Krummrich
2025-09-08 9:21 ` Miguel Ojeda
2025-09-08 10:22 ` Alice Ryhl
2025-09-08 11:13 ` Miguel Ojeda
2025-09-08 11:15 ` Miguel Ojeda
2025-09-10 1:09 ` John Hubbard
2025-09-10 2:50 ` Miguel Ojeda
2025-09-10 19:40 ` John Hubbard
2025-09-10 19:42 ` Danilo Krummrich [this message]
2025-09-11 2:33 ` Alexandre Courbot
2025-09-12 23:31 ` John Hubbard
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=0d8b8918-fe90-4eca-989a-d24cf95c1dd5@kernel.org \
--to=dakr@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=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=vitaly.wool@konsulko.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox