From: Ritvik Gupta <ritvikfoss@gmail.com>
To: Gary Guo <gary@garyguo.net>
Cc: ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH v2] rust: kernel: introduce `unsafe_precondition_assert!` macro
Date: Thu, 31 Jul 2025 00:07:49 +0530 [thread overview]
Message-ID: <aIpmfRIvGh8oVUUj@fedora> (raw)
In-Reply-To: <20250730181420.6979b4f1@eugeo>
> This email should be include the Rust-for-Linux list.
Apologies for oversight.
Automated it to prevent in future :)
> These can just be `const { assert!() }`? There's no reason for this to
> be runtime.
Yeah! `static_assert!` makes sense here.
I'll add more relevant example in v3.
Thanks for the feedback :)
prev parent reply other threads:[~2025-07-30 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 17:11 [PATCH v2] rust: kernel: introduce `unsafe_precondition_assert!` macro Ritvik Gupta
2025-07-30 17:14 ` Gary Guo
2025-07-30 18:37 ` Ritvik Gupta [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=aIpmfRIvGh8oVUUj@fedora \
--to=ritvikfoss@gmail.com \
--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=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=skhan@linuxfoundation.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