Types and Erlang: from Dialyzer to(...)
summary
Explains why strict typing fails for Erlang: hot code swapping, asynchronous message passing and process identifiers that can point to anything break assumptions a static type system needs. Describes building and using Dialyzer — an optional, gradual analyser that reports only definite errors — with a concrete example where a map key expected an integer but a float is passed and Dialyzer flags it. Proposes session types as a way to type communication protocols, showing a tiny shop protocol that models add versus checkout flows.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:03The fittings of a function
- 2:05Breach of contract
- 3:09Composing a program
- 5:11Reasons for not typing Erlang
- 8:00The byte of '97
- 14:03They tried having less expectations
related talks
31mTIL By Breaking Production...
36mOperable Erlang and Elixir
23meqWAlizer - Scaling Erlang development at WhatsApp with static typing
38mLanguage Reliability Illustrated by Elixir and Erlang
01h 03mThinking Erlang in a connected world
03h 19mWorkshop - All Aboard The Elixir Express!
34mInfERL: Scalable and Extensible Erlang Static Analysis
52mWrite Less, Do More (and Have Fun!) with Elixir Macros