forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 489
Add unsafe_precondition_assert! #1162
Copy link
Copy link
Closed
Labels
easyExpected to be an easy issue to resolve.Expected to be an easy issue to resolve.good first issueGood for newcomersGood for newcomersmediumExpected to be an issue of medium difficulty to resolve.Expected to be an issue of medium difficulty to resolve.• libRelated to the `rust/` library.Related to the `rust/` library.
Metadata
Metadata
Assignees
Labels
easyExpected to be an easy issue to resolve.Expected to be an easy issue to resolve.good first issueGood for newcomersGood for newcomersmediumExpected to be an issue of medium difficulty to resolve.Expected to be an issue of medium difficulty to resolve.• libRelated to the `rust/` library.Related to the `rust/` library.
See https://lore.kernel.org/rust-for-linux/CANiq72mi47p0jVoXXq1d1G+7PnHi7ngs6zTS084igfZZzzNGBw@mail.gmail.com/.
Like #1159, but for
unsafe_precondition_assert!.The name mimics other
{kind}_assert!s likedebug_assert!, as well ascore's ub-checks one (assert_unsafe_precondition!).Please double check if there are already asserts out there (or perhaps even new ones) that could make use of it, and transform (or add) them in a second patch etc.
This requires submitting a proper patch to the LKML and the Rust for Linux mailing list. Please recall to test your changes (including generating the documentation if changed, running the Rust doctests if changed, etc.), to use a proper title for the commit, to sign your commit under the Developer's Certificate of Origin and to add a
Suggested-by:tag, and aLink:tag to this issue. Please see https://docs.kernel.org/process/submitting-patches.html and https://rust-for-linux.com/contributing for details.