From: John Hubbard <jhubbard@nvidia.com>
To: Alexandre Courbot <acourbot@nvidia.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"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: Fri, 12 Sep 2025 16:31:07 -0700 [thread overview]
Message-ID: <d45454c1-44a1-4e47-a3ef-2ff37d529235@nvidia.com> (raw)
In-Reply-To: <DCPMBM7DOG2Y.9N56KZVVO7GC@nvidia.com>
On 9/10/25 7:33 PM, Alexandre Courbot wrote:
> On Thu Sep 11, 2025 at 4:40 AM JST, John Hubbard wrote:
>> On 9/9/25 7:50 PM, Miguel Ojeda wrote:
>>> On Wed, Sep 10, 2025 at 3:09 AM John Hubbard <jhubbard@nvidia.com> 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.
>>
>> Is there some sort of exception to the "min Rust version"? I haven't
>> figured out where that is written down.
>
> My understanding is that while the feature enabling this syntax
> (`raw_ref_op`) is stable since 1.82, it has been introduced as an
> unstable feature before 1.78. So it is here, just not enabled by
> default before 1.82.
aha, that's the key point that I was missing.
>
> R4L enables some of these unstable features when needed, especially
> since they have been stabilized meanwhile. For instance, we did it with
> the `pointer_is_aligned` feature for the `FromBytes` patch [1].
>
OK, I see. Thanks for explaining!
thanks,
--
John Hubbard
prev parent reply other threads:[~2025-09-12 23:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 14:02 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
2025-09-11 2:33 ` Alexandre Courbot
2025-09-12 23:31 ` John Hubbard [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=d45454c1-44a1-4e47-a3ef-2ff37d529235@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--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=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
all inboxes | Powered by JetHome®