[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=2mspecUmNVr31b+hAr4Q46Qg3UbiLKkis4D2WjJzYJw@mail.gmail.com>
Date: Sat, 17 Jan 2026 20:16:15 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Gary Guo <gary@...yguo.net>
Cc: Alexandre Courbot <acourbot@...dia.com>, Alice Ryhl <aliceryhl@...gle.com>,
Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: ptr: replace unneeded use of `build_assert`
On Sat, Jan 17, 2026 at 5:49 PM Gary Guo <gary@...yguo.net> wrote:
>
> static_assert! creates an item and thus cannot refer to generic parameters.
Ah, right, thanks Gary -- you were the one removing that limitation
from const blocks years ago!
Since we are here, I wondered about whether there was progress on
allowing top-level inline const so that we could perhaps use that for
a macro that can do both (or just use the inline const syntax
everywhere, but `rustfmt` may employ three lines...), i.e. this one I
had linked in our usual list:
https://github.com/rust-lang/lang-team/issues/251
But I see someone recently created a tracking issue and even an
implementation PR (without commenting in the above issue, which makes
it hard to notice). It actually seems close to landing:
https://github.com/rust-lang/rust/issues/149226
https://github.com/rust-lang/rust/pull/149174
There is/was an early experiment on omitting `: ()` on const items as well:
https://github.com/rust-lang/rust/pull/149738
Cheers,
Miguel
Powered by blists - more mailing lists