From: Benno Lossin <benno.lossin@proton.me>
To: Altan Ozlu <altan@ozlu.eu>, Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"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>,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v4] rust: static_assert: add optional message
Date: Thu, 27 Mar 2025 22:41:38 +0000 [thread overview]
Message-ID: <D8RESWOSOSY0.1W6K6HZ4IMIQI@proton.me> (raw)
On Wed Mar 26, 2025 at 9:25 PM CET, Altan Ozlu wrote:
> Add an optional panic message to the `static_assert!` macro.
>
> The panic message doesn't support argument formatting, because the
> `assert!` macro only supports formatting in non-const contexts.
>
> Suggested-by: Miguel Ojeda <ojeda@kernel.org>
> Link: https://github.com/Rust-for-Linux/linux/issues/1149
> Signed-off-by: Altan Ozlu <altan@ozlu.eu>
Reviewed-by: Benno Lossin <benno.lossin@proton.me>
---
Cheers,
Benno
> ---
> Link to v3: https://lore.kernel.org/rust-for-linux/20250325211011.1093374-2-altan@ozlu.eu/
> ---
> rust/kernel/static_assert.rs | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
next reply other threads:[~2025-03-27 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:41 Benno Lossin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-26 20:25 [PATCH v4] rust: static_assert: add optional message Altan Ozlu
2025-04-15 19:26 ` Altan Ozlu
2025-04-15 19:30 ` Miguel Ojeda
2025-04-15 20:17 ` Altan Ozlu
2025-04-17 7:42 ` Trevor Gross
2025-04-17 10:53 ` Miguel Ojeda
2025-05-12 13:48 ` 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=D8RESWOSOSY0.1W6K6HZ4IMIQI@proton.me \
--to=benno.lossin@proton.me \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=altan@ozlu.eu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).