Mar 24
Loading video player...
Go will let nil compile, ship, and panic in production. Rust will not let you write that program in the first place. In Go every pointer can be nil. The compiler never forces you to check. You find out at runtime when your server crashes with a nil pointer dereference on a line that looked completely safe an hour ago. Rust has no nil. If a value might be absent you wrap it in Option and the compiler refuses to build any code that uses the inner value without first proving it exists. The absent case is not a runtime surprise. It is a type. What you will learn: → Why Go nil is a compiler blindspot not just a developer mistake → How Option models absence at the type level → Why if let is safer than unwrap and when each one makes sense → How the same bug looks in Go vs Rust side by side This is for developers who already write Go or Rust and want to understand the concrete difference in how each language handles missing values, not a theory lecture. Timestamps: 0:00 Go nil: compiles fine, panics at runtime 0:08 The nil pointer dereference in practice 0:16 Rust Option forces you to handle absence 0:24 Running the safe version Resources: → Rust Option docs: https://doc.rust-lang.org/std/option → Rust book on enums and Option: https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html #Rust #Golang #RustVsGo #NullSafety #RustLang #GoLang #LearnRust #LearnGo #SystemsProgramming #BackendDevelopment