Rust 101 – 44: Undefined behaviour
Share on Mastodon
If you write unsafe Rust, you need to reason about “undefined behaviour”. We talk through what that means, and try to develop an intuition about why we can’t predict how our program will behave if we don’t follow the rules.
Series: Language basics, More syntax, Traits and generics, Building applications, Concurrency and parallelism, Trait objects, Async, Unsafe
This section (Async): 42: Why unsafe?, 43: Meaning of unsafe, 44: Undefined behaviour
Links:
- Slides: Rust 101 – module F
- Exercises: artificialworlds.net/presentations/rust-101/exercises/F-safe-unsafe/mod.html
The course materials for this series are developed by tweede golf. You can find more information at github.com/tweedegolf/101-rs and you can sponsor the work at github.com/sponsors/tweedegolf. They are released under the Creative Commons Attribution Share Alike 4.0 International license.
This series of videos is copyright 2024 Andy Balaam and the tweede golf contributors and is released under the Creative Commons Attribution Share Alike 4.0 International license.