Safety without a collector.
WHAT IT IS
A statically typed compiled language providing memory safety without garbage collection.
HOW IT ACHIEVES THAT
An ownership system, enforced at compile time.
WHAT OWNERSHIP MEANS
Each value has one owner, and is released when the owner goes out of scope.
WHAT BORROWING MEANS
Temporary access to a value, with rules preventing conflicting access.
WHAT THAT PREVENTS
Use after freeing Double freeing Data races between threads
WHY THAT LAST ONE IS REMARKABLE
Data races become compile-time errors rather than intermittent runtime faults.
WHAT IT COSTS
A genuinely steep learning curve Longer compilation times More effort to satisfy the compiler initially
WHAT PEOPLE REPORT
Fighting the compiler at first, then finding it prevents real bugs.
WHAT ELSE IT PROVIDES
A strong type system with pattern matching Errors as values, handled explicitly Excellent tooling and package management
WHAT IT IS USED FOR
Systems programming Infrastructure components Performance-critical services Increasingly, anywhere C or C++ would have been used
WHO IT SUITS
Teams where correctness and performance both matter.
