Wyzer-Lang Unveils Statically Typed Language Aiming for Unified Safety Model
Developers behind the Wyzer programming language argue that a single ownership rule can replace complex borrow checkers and garbage collectors, though the project remains in early research stages.
The Wyzer-Lang group has released Wyzer, a new statically typed and compiled programming language, via a "Show HN" post on Hacker News. The project aims to deliver safety comparable to Rust without relying on a garbage collector or a complex borrow checker. By utilising a single ownership rule, the language seeks to manage memory, concurrency, and network safety within a unified framework.
Wyzer employs choreographic programming to enforce distributed safety and utilises a Perceus memory model. The developers state that most critical bugs, such as memory leaks and deadlocks, stem from unclear resource ownership. Consequently, the language applies one strict rule across memory, threads, and networks: once a resource is used, it cannot be used again. This approach intends to eliminate the need for separate tools to handle different types of system safety.
The language features immutable variables by default, declared using `let`, with mutable variables requiring an explicit `var` declaration. Compile-time constants are handled via `const`. Unlike many modern languages, Wyzer does not use parentheses around conditions in standard control flow structures such as `if/else`, `while`, and `for` loops. The design philosophy, attributed to Atiksh Sharma, emphasises that simplicity is power without pretense.
Error handling in Wyzer avoids hidden exceptions or an `async/await` split. Instead, functions that can fail return a `Result` type, which developers must handle using `match` expressions. This ensures that both success and error cases are visible in the code. The developers note that while Rust guarantees safety within a process, it lacks native network safety features, which Wyzer attempts to address through its choreographic programming model.
Despite its ambitious goals, the project is currently in early research stages. The Wyzer-Lang group acknowledges that several significant problems remain unsolved and that the language is not yet production-ready. The code is available on GitHub, and the community engages via a Discord server, with contributions welcome for those interested in the underlying research.
