PIMP MY IDEBack to dispatches
October 11, 2026 / language design / prototype inspection

A reference should carry its survival route.

Valen is testing a borrow checker that remembers where references point. That can permit mutable aliases while still rejecting use after invalidation.

The interesting unit is the path. Review the owner, descendant route, invalidating action, and later use together.

Track where the reference points

Valen's author describes a group-borrowing model in which the compiler records a path for each reference. A reference to world.entities[0] carries a route through the owner, field, and item. If a later action replaces world.entities, that route no longer reaches the original item. A later use can then be rejected as an invalidated borrow.[1]

This is a different review question from counting mutable references. Ask whether an action breaks the recorded route before the next use.

Mutable aliasing is not the whole safety question. The lifetime of the route matters.

Function contracts carry invalidations

The proposal moves part of the safety model into function signatures. The caller needs to know which paths a call may invalidate. That can admit patterns used by C++ and reference-counted systems, but it also makes contract quality part of memory safety.[1]

Carbon's November 2025 project update confirms the trade. Its team was researching effect-annotated approaches influenced by group borrowing because they may prove more C++ patterns safe. The same update says the approach increases the complexity of function contracts.[3]

Prototype means prototype

The Valen repository calls the language a prototype that is barely past proof of concept. It says version 0.1 will come after the project is stable enough to use. The README documents a source build for a small program and warns that Rust interoperation needs a modified Rust compiler.[2]

We inspected revision 54794d0fce4691102e18641e46ca7f26574baa54. We did not build or run the compiler because the inspection host had no Rust toolchain. The article's examples and reported behavior remain author evidence. They are not an independent conformance result.

Review the route before the slogan

A useful code review card for any path-aware model has four fields. Record the owner. Record the exact descendant path. Name the action that may invalidate it. Name every use that follows. Then attach the real compiler revision and diagnostic.

The bench below teaches that reading order. It does not implement Valen's checker, parse source, or predict compiler behavior.

Interactive teaching fixture

Borrow-path inspection bench

Traditional purpose: a language-rule note, scenario picker, path diagram, and review card. The native controls share one state. The result names the teaching case without claiming a compiler verdict.

OwnerPathActionLater use

Set the teaching case

Choose one action after borrowing world.entities[0]. Select the contract sections your real review card will require.

Choose an action after the borrow
Select review-card sections
TEACHING CASE0 of 4 sections selected

Path readout

Another alias reads the descendant. This fixture leaves the path connected.

Recorded pathRead alias
PATH SHOWN / NO COMPILER VERDICTThe route remains visible in this teaching case. Check the real function contract and compiler output.
Sources read / October 11, 2026 UTC

Source log

Open the evidence boundary
  1. Evan Ovadia, "Valen's Memory Safety: A New Kind of Borrow Checking", published and read October 11, 2026. This supplies the author's description of path tracking, invalidation, mutable aliasing, and function-signature effects. Its compiler examples are author evidence.
  2. Valen repository at revision 54794d0fce4691102e18641e46ca7f26574baa54, inspected October 11, 2026. The README labels Valen a prototype, documents the basic source build, and warns that Rust interoperation uses a modified compiler. GitHub's API reports Apache-2.0 and main as the default branch.
  3. Carbon Copy No. 9, November 2025, read October 11, 2026. This supports Carbon's stated research interest in effect-annotated memory safety influenced by group borrowing. It also states the function-contract complexity trade.
  4. Hacker News discussion, item 50042362, verified through the official HN API and read October 11, 2026. We used it only as a current-interest signal.

Evidence boundary: Pimp My IDE read the named article, repository page at the pinned revision, Carbon project update, and discussion. We did not build Valen, run the examples, audit the compiler, or verify memory safety. The interactive bench is a teaching model and review-card generator.