Erlang

FunctionalDynamicGC

Built for telecom reliability — powers WhatsApp, RabbitMQ, and systems that need 99.999% uptime. The actor model and "let it crash" philosophy make concurrency natural. Among the highest guardrail scores thanks to immutable data, process isolation, and pattern matching that eliminates most null/race/overflow bugs.

Quality

Concept Distribution

Safety4.7 / 5

Memory

Compile-time

BEAM VM GC + immutable data prevent memory corruption

Null

Runtime

Pattern matching handles absence; badmatch at runtime

Data Races

Compile-time

Actor model — no shared mutable state, process isolation

Overflow

Compile-time

Arbitrary-precision integers — overflow impossible

Coercion

Compile-time

No implicit conversions — explicit conversion functions

Compile-timeRuntimeOpt-inNone

How we score

Expressivenessavg across benchmarks

Lines

12

Verbosity

257

Ceremony

0

Surface Area55 concepts

28 reserved keywords

Types

6

Control

8

Functions

8

OOP/Data

4

Memory

2

Concurrency

15

Metaprog

6

Errors

6

How we measure

Explicitness

51% explicit49% implicit

51% of 55 concepts have dedicated keyword syntax. The rest are learned through documentation and practice.

AI Readiness

Type Coverage

Dynamic

LLM Tokens

121

Tok/Line

10.1

Lower tokens = cheaper API calls. Higher type coverage = more for AI to work with.

Solutions

View all Erlang solutions in the problem pages.