Crossing boundaries with Gleam - from functions to runtime
summary
A functional chess engine is built in Gleam with opaque types, pattern matching and a rules engine, compiled to Erlang and loadable in IEx via compile to Erlang. Unit tests assert a knight at D4 has 8 valid moves. Rendering uses Scenic inside an Elixir app (mix gleam, Registry, DynamicSupervisor) so game state runs in processes; a Gleam actor shapes session messages but the Scenic client currently controls only one game. Integration works end-to-end but multi-session UI is unfinished.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 6:44Gleam for chess
- 11:24Design challenges and types
- 12:47Functional core to UI
- 14:57Gleam with Elixir OTP
- 17:46Closing remarks
- 18:31Q&A
related talks
38mA Code Centric Journey Into the Gleam Language
46mBuild Your Own Elixir
35mDeriving an Erlang Interpreter from a Mechanised Formal Semantics of Core Erlang
29mTowards Exact Semantic Equivalence of Erlang BEAM Constructs: Lessons from Advanced(…)
32mExperience Report: Graph Rewriting with Lexical Effect Handlers
01h 21mGrails 3.x Inside and Out
14mAchieving High-Performance the Functional Way - A Functional Pearl on Expressing High...
50mOne VM to Rule Them All