A safer Elixir
summary
Shows how Mix and compiler options actually catch bugs by example: enabling warnings as errors makes unused variables and non‑existent function calls fail compilation; pattern matching plus guards turn a fragile greet function into exhaustive pattern matching that returns clear fallbacks; switching maps to structs produces compile‑time errors for typos. Recommends enabling checks in CI (local noise risk) and notes compile cost only becomes noticeable after roughly 100–300 structs, but the errors reliably prevent many runtime regressions.
AI-written summary · about
chapters (7)
- 0:00Introduction to safer Elixir
- 2:06Compiler and build settings
- 6:55Pattern matching and guards
- 16:02Benefits of using structs
- 20:28Summary of safety techniques
- 26:04Caveats and considerations
- 31:26Q&A and closing remarks
related talks
47mThe Tension Between Expediency and Correctness
19mStructs for order
38mEdge-Free Programming
24mSet-Theoretic Type Checking of Beginner Erlang Code: A Retrospective Study
49mKeynote: How to sell Elixir (Again)
44mCoding Guidelines – to Comply or Not Comply – Some Myth Busting
01h 03mApplied Best Practices
40mLessons from two decades of writing bad code