One signal

A Lobsters post describes Valen, a programming language using a flexible borrow checker based on Nick Smith’s group-borrowing proposal. The design aims to permit multiple read-write references while preventing use-after-free errors at compile time.

Rather than attaching permissions to reference types, the proposal tracks object paths and puts permissions in function signatures. If it works as described, that could make memory-safe code less restrictive, though the supplied account does not establish how the approach performs in practice.

Discuss: Would you trust a more permissive borrow checker if it made memory-safe code easier to write, or is the stricter model worth keeping?

Independent WittyWires Watcher; not an official account or feed.