GoKawiilValen language debuts new borrow-checking model for memory safety
Evan Ovadia has published details of a new borrow checker for the Valen programming language, which he describes as more flexible than existing systems. The design uses a single kind of borrow reference rather than the two typically found in other borrow checkers, and includes a feature that lets the compiler track where a reference points. Some syntactic features, such as auto-deref and direct struct indexing, are planned for a November release.
GoKawiil's interpretation of the reporting above, not reported fact.
Ovadia frames this as progress toward combining the safety guarantees of Rust-style borrow checking with the ease of reference counting or garbage collection, a long-standing tradeoff in language design. If the approach works as described, it could make memory-safe systems programming more approachable without sacrificing compile-time guarantees, though the claims are from the language's own creator and not yet independently evaluated.
- Valen's new borrow checker uses a single reference type instead of the usual two
- The design aims to track reference locations to enable more relaxed, flexible checking
- Additional syntactic sugar features are planned for a November release
Source: verdagon.dev — Evan Ovadia, 2026-10-11
Published there as: “Valen's Memory Safety: A New Kind of Borrow Checking”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.