A first look at token efficiency
Jappie:
if you’d start desining a language with an LLM as the primary user in mind
This exists actually. I haven’t tried it yet but the features are pretty interesting:
github.com
GitHub - jasisz/aver: Aver is a programming language for auditable...
Aver is a programming language for auditable AI-written code
Aver
Aver is a statically typed language designed for AI to write in and humans to review, with a bytecode VM for runtime execution, a Rust backend for deployment, a WASM backend for browser and embedded targets, Lean proof export for pure logic and classified effectful laws, and Dafny verification for automated law checking via Z3.
It is built around one idea: the risky part of AI-written code is usually not syntax, it is missing intent. Aver makes that intent explicit and machine-readable:
effects are part of the function signature
decisions live next to the code they explain
pure behavior lives in colocated
verifyblocksselected effectful behavior can be verified with explicit stubs and trace assertions
effectful runs can be recorded and replayed deterministically
aver whyscores every function’s justification coverage: description, verify, decisionsaver auditruns all three axes — static checks, verify execution, format compliance — as a single CI gateaver contextexports the contract-level view of a module graph for humans or LLMsaver compileturns an Aver module graph into a Rust/Cargo project or a standalone WASM moduleaver proofexports the pure subset of an Aver module graph to a Lean 4 proof project (default) or Dafny verification file (--backend dafny)
This is not a language optimized for humans to type by hand all day. It is optimized for AI to generate code that humans can inspect, constrain, test, and ship.
Discussion in the ATmosphere