We introduced recently unsafe_precondition_assert!, and it would be nice to add new use cases and/or migrate existing ones to it.
In other words, please search for places where the new unsafe_precondition_assert! can be applied, and/or check existing debug_assert!s that may be renamed.
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 a Link: tag to this issue. Please see https://docs.kernel.org/process/submitting-patches.html and https://rust-for-linux.com/contributing for details.
We introduced recently
unsafe_precondition_assert!, and it would be nice to add new use cases and/or migrate existing ones to it.In other words, please search for places where the new
unsafe_precondition_assert!can be applied, and/or check existingdebug_assert!s that may be renamed.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.