[ ] I've added tests for all code changes and additions (where applicable)
[ ] I've added a demonstration of the new feature to one or more examples
[ ] I've updated the book to reflect my changes
[ ] Usage of new public items is shown in the API docs
API changes
In this function you use the unsafe keyword for one safe expression.
We need to mark unsafe operations more precisely using unsafe keyword. Keeping unsafe blocks small can bring many benefits. For example, when mistakes happen, we can locate any errors related to memory safety within an unsafe block. This is the balance between Safe and Unsafe Rust. The separation is designed to make using Safe Rust as ergonomic as possible, but requires extra effort and care when writing Unsafe Rust.
Hope this PR can help you.
Best regards.
Referenceshttps://doc.rust-lang.org/nomicon/safe-unsafe-meaning.htmlhttps://doc.rust-lang.org/book/ch19-01-unsafe-rust.html
Checklist
API changes
In this function you use the unsafe keyword for one safe expression.
We need to mark unsafe operations more precisely using unsafe keyword. Keeping unsafe blocks small can bring many benefits. For example, when mistakes happen, we can locate any errors related to memory safety within an unsafe block. This is the balance between Safe and Unsafe Rust. The separation is designed to make using Safe Rust as ergonomic as possible, but requires extra effort and care when writing Unsafe Rust. Hope this PR can help you. Best regards. References https://doc.rust-lang.org/nomicon/safe-unsafe-meaning.html https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html