Wyzer is a statically typed, compiled programming language designed to provide safety guarantees for memory, threads, and network interactions through a unified ownership model. According to the project’s GitHub repository, the language aims to solve hard problems like memory bugs, deadlocks, and network errors by ensuring clear resource ownership, inspired by the idea that most such issues arise from unclear ownership of resources. Wyzer uses Perceus reference counting for fast memory management without garbage collection or complex borrow checking, a technique borrowed from Koka and Lean 4. For network safety, it employs choreographic programming, which allows developers to write a single rule that generates correct communication code for all participants, preventing deadlocks and message mismatches before runtime. This same ownership rule is extended to handle threads and hardware interrupts, meaning one concept governs memory, concurrency, and network safety. The language emphasizes simplicity and explicitness: variables are immutable by default, requiring var for mutability and const for compile-time constants. Error handling is explicit via Result<T, E> types and match expressions, which must include a trailing semicolon when used as statements. Wyzer avoids hidden control flow, such as async/await splits, and returns errors as standard types. While acknowledging influences from Rust, Go, Java, and Python, Wyzer positions itself as an alternative that offers Rust-like safety without its steep learning curve and avoids the unpredictability of garbage-collected languages for low-level or real-time systems. The project notes it is still in early research stages, with several unsolved problems, and encourages contributions via its Discord server and documentation. AI assistance was used in generating commit messages, researching choreographic programming and Perceus, and designing the language’s branding, including its logo.
Key facts
- Wyzer is a statically typed, compiled, resource-oriented programming language.
- It uses Perceus reference counting for memory management, borrowed from Koka and Lean 4.
- It employs choreographic programming to ensure network, thread, and interrupt safety through a single ownership rule.
- Variables are immutable by default; mutability requires explicit use of
var. - Error handling uses
Result<T, E>andmatchexpressions with required trailing semicolons when used as statements. - The language aims to provide Rust-like safety without a steep learning curve or garbage collector overhead.
- Wyzer is currently in early research phase with known unsolved problems.
- AI was used to assist with commit messages, research, and logo design.