Reading through
|
//! The below implementation is a bit of a compromise in trying to help new devs |
, I see unsafe blocks labeled with SAFETY comments, which is great! However, the comments focus on why the unsafe block is required (eg. a specific FFI call or unsafe API method), rather than what preconditions ensure the unsafe code is actually safe in practice.
Reading through
Windows-rust-driver-samples/general/echo/kmdf/exe/src/main.rs
Line 4 in d9cc309