01
Types, unasked
Annotations are optional. Unannotated code is inferred anyway — for speed and correctness both. Nothing falls back to an interpreter.
Playground
fn fib(n) { fib(n-1) + fib(n-2) }fn fib(1) { 1 }fn fib(0) { 0 }fn fibSequence(n) {xs = []for i = range(1, n) {append(&xs, fib(i))}return xs}show fibSequence(10)
output
awaiting invocation_
Powers
02
Ints are library code
Integers, bytes, even malloc are written in Raven itself. Layout and allocation are yours when you want them.
03
Values first
Compound data is immutable by default. The swap operator keeps mutation's convenience; changes never turn up somewhere you didn't ask.
04
Multiple dispatch
One name, many definitions, selected by matching the arguments — types, values or structure.
05
No coloured functions
No async, no await, no codebase cut in half. Any code can suspend.
06
Incremental throughout
The pipeline rebuilds only what moved: fast builds, live REPL, notebooks, tooling that keeps pace.
Where it runs
- wasm
- The browser, sandboxed by default. Safe enough to run code an LLM wrote.
- native
- Serverless functions and CLI tools, compiled ahead of time.
- js
- Reach the DOM or npm with no glue code, and export Raven functions back out.
One line to start
$ npm i -g @unkindnesses/raven$ raven> 2+24> Complex(1, 2) / 20.5 + 1.0im> factorial(big(50))big(3041409320171337804361260816606476884377641568960512…)