RustCurious 1: Why Rust is Safe
Rust is a systems language with just as much control and performance as C or C++. And yet, it guarantees memory safety and thread safety at compile-time. How is that possible? Complete Rust course: • All Lessons 🚀 https://rustcurious.com 00:00 Fast, full control, and safe? 01:52 Safe vs unsafe 04:59 Thought experiment language: C without pointers 07:47 Move-only types protect resources by preventing implicit copy 11:13 Borrowed references are safe pointers for temporary exclusive access 16:46 Review, copyable vs move-only types 20:19 Safe heap-allocated memory 23:25 Regions enable returning a borrowed reference from a function 28:23 Shared references allow aliased read-only access 32:30 Mutable XOR shared - multiple readers or one writer 35:28 Thread safety is enforced at compile-time 37:46 Learning actual Rust

RustCurious 2: Hello Rust – Basic Syntax

RustCurious 9: Traits are Interfaces

Why Rust is different, with Alice Ryhl

Understanding Rust – Or How to Stop Worrying & Love the Borrow-Checker • Steve Smith • YOW! 2024

RustCurious 6: Enums and Polymorphism

How Much Memory for 1,000,000 Threads in 7 Languages | Go, Rust, C#, Elixir, Java, Node, Python

RustCurious 7: Arrays and Slices

Engineer Answers Rust Questions | "Compile Time"?

Stop Saying Rust Is Too Complicated

Will Crichton: Rust for Everyone!

14 Rust Smart Pointers Compared

RustCurious 8: Generics and Monomorphization

A Simpler Way to See Results

Async Rust explained in 20 minutes

RustCurious 4: Structs and Resources

Rust and the price of ignoring theory

Rust for the impatient

Rust Is Not as Safe as You Think It Is: Improving Safety and Reliability in Rust -Colin Breck JOTB25

How Rust engineered the perfect async runtime

