A Brazilian systems programming language focused on memory safety, clean syntax, explicit errors, and native tooling.

Explore the compiler · Roadmap · Contributing · Releases

Arandu is an experimental systems programming language. It takes ideas that are proven elsewhere and aligns them with a pragmatic, deterministic model:

• Memory safety by default — safe ref T / mut ref T references, owned values, and unsafe only where raw ptr[T] is used; ownership is a compiler-enforced proof, not a style rule.
• Clean, readable syntax — strict casing rules (camelCase values, PascalCase types) let the parser tell values apart from types, keeping the grammar small and explicit.
• Explicit errors — Result<T, E> and Option<T> on the surface, with ?, defer, and errdefer for clear control flow instead of hidden exceptions.
• Native tooling — a single arandu CLI handles new, check, run, build, fmt, and doctor, backed by an incremental Salsa query DB and an LSP for editors.

arandu new hello
cd hello
arandu run

Installation archives ship from GitHub Releases on v* tags. The full dependency-free compilation flow (no LLVM) starts with arandu build.

• Compiler foundation gold — AMIR TypeId, spans, target-aware DataLayout, host C↔Cranelift parity, unified imports, recovery, and endurance are protected by CI.
• Product surface — Arandu Minimal 0.1 and the project CLI (new / check / run / build / doctor) are gold in their published scope.
• Coming next — full ownership surface, user Display / custom formatting, and production C polish / freestanding runtime.

See the single execution roadmap for details.

We welcome all forms of contribution: bug reports, feature suggestions, documentation, tests, and code. Start with our contributing guide and the compiler docs.

Read the Code of Conduct before interacting with the community.

Arandu is dual-licensed under MIT and Apache 2.0 — pick the terms that suit you best.