Unsafe Rust: How and when (not) to use it

Description

Summary

• Andre Bogus FollowAndre "llogiq" Bogus is a Rustacean (yes, that's his official title) for Storyscript, a Rust contributor, and Clippy maintainer.
• This is usually not meant to be used from the outside, but it can sometimes be public because people might use unsafe methods in their code if they want to assume the ensuing responsibility in exchange for performance (or other things).
• To allow this, Rust has blessed a (unsafe, of course) type with interior mutability — you can get a mutable pointer (not reference, of course) from an immutable borrow using the get(&self) method.
• All of them are defined as unsafe, mainly because they may not be implemented on your CPU.