`@gc` is no longer part of the language: a developer never writes or mentions
it. GC-ness is decided entirely by inference (structural cycles + demand
promotion), which the earlier 7b commits made complete and precise.
- parser: `@gc` on a class is now WO-E104 ("GC-ness is inferred; run
`woc --dump-gc`. Remove it."). `is_gc` stays false; the class classifies by
inference. No `.wo` in the repo carries `@gc` anymore.
- types.ml: retired the WO-W201 machinery (suggest_gc_annotation,
has_recursive_structure(_type), has_unique_field, gc_suggestion_code) — it
suggested `@gc`, now obsolete since inference traces exactly those classes.
- runner.ml: deleted the 8 WO-W201 gc-suggestion test blocks; the @gc-exemption
test's `Cache` is made self-referential so inference classifies it gc without
an annotation.
- fixtures: dropped `@gc` from rc.wo (Cache demand-promotes via its escape),
elision.wo (Cache given a self-ref to stay structurally gc for the rc-elision
dump), pricing-demo.wo (PriceCache doesn't escape -> now owned), and the
abandoned-cycle/budget-steps corpus (Node is structurally gc). rc.wo keeps a
placeholder comment line so its line-indexed rc assertions hold. Goldens
re-blessed.
- docs: error catalog gains WO-E104 and marks WO-W201 retired; gc-cycle README
records the keyword removal.
Verified: woc-test 553/0 (was 566 minus the 13 retired WO-W201 checks),
test_diag 14/0, oop-e2e 79/0, employee 8/0, log-watcher 7/0. `git grep '@gc'`
finds only comments — success criterion 1 met.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| 00-wob-format.md | ||
| 01-error-catalog.md | ||
| 02-corpus.md | ||
| 04-db-binding.md | ||
| 08-builtin-surface.md | ||
| README.md | ||
docs/plan/oop-vm/ — OOP + systems track contracts
The normative contract documents both stacks cite. Landed by their named plan tasks:
| doc | contract | plan |
|---|---|---|
00-wob-format.md |
.wob bytecode format (compiler↔VM) |
1 |
01-error-catalog.md |
every WO-E### code |
2, grows 3/8 |
02-corpus.md |
how to add conformance fixtures | 3 |
03-shard-actor.md |
shard ownership, mailboxes, send-as-move | 4 |
04-db-binding.md |
row format, WAL records, query subset | 5 |
05-http-service.md |
route section, trap→HTTP table, JSON subset | 6 |
06-ui-live.md |
delta frames, subscribe protocol, wo:live | 7 |
07-systems-stdlib.md |
per-function nil-vs-trap contracts | 9 |
08-builtin-surface.md |
builtin source names, container/call/entry rules the emitter enforces | 3 |
Specs and plans: docs/superpowers/{specs,plans}/. Repo map: docs/08-project-structure.md.