PEGO
A170: Operators Rule Attempt Scratch
Trying every operator candidate should not allocate a fresh attempt object and capture-save slice for each try.
Mechanism and Invariants
longest keeps the best attempt by value and uses a parser-owned buffer to save
captures across reset. The winner still follows longest match and
declaration-order ties. Iterative execution passes the attempt through dedicated
parser/frame state instead of enlarging every generic step result. Scratch
cannot alias the winning published value or erase live captures.
Scope and State
Default Go Operators Rule routes in closure, both VMs and generated Node/typed Go. TypeScript uses its own JavaScript candidate objects; Go by-value attempt allocation is not applied there.
Reference Control
No independent maintained same-source per-candidate allocation control exists.
Evidence and Implementation
Records 011/013 measure lower Minilang/Operators allocation counts. Record 013 also records a rejected generic-result layout that slowed the iterative VM about 20%. The adopted route's historical effects do not imply every Operators Rule allocation is eliminated.
Source owners: parser.longest and saved captures, Operators Rule attempt state, generated longest, typed Operators Rule attempts.
The comparison policy distinguishes same-source controls, historical changes and full checkpoints.