Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Since you are a C++ programmer, I would've shown you this blog series (Learn Rust the Dangerous Way) and this book about writing linked lists in Rust (Too Many Lists). Those uses unsafe and explain the safety preconditions and best practices when writing unsafe code.
Have you read the nomicon? I'm not sure it fits "in between," but it's definitely not on the "BNF and little explanation" spectrum of things. But if you're coming from years of C or C++ and are totally cool with raw pointers and just want to do stuff with them, then I'd probably point you to the nomicon.
The reality is that I have used unsafe that is also unsound out of convenience because fixing it is a papercut too many. And this tends to be common! I know enough to spot unsoundness in other projects (sometimes even early). But not enough to be confident in my own abilities to write sound unsafe code. Why? Because it's really flipping hard, that's why!
The reality is that I have used unsafe that is also unsound out of convenience because fixing it is a papercut too many. And this tends to be common! I know enough to spot unsoundness in other projects (sometimes even early). But not enough to be confident in my own abilities to write sound unsafe code. Why? Because it's really flipping hard, that's why!
The reality is that I have used unsafe that is also unsound out of convenience because fixing it is a papercut too many. And this tends to be common! I know enough to spot unsoundness in other projects (sometimes even early). But not enough to be confident in my own abilities to write sound unsafe code. Why? Because it's really flipping hard, that's why!