Answer architecture round 2: a keyed walk position, a plainer Above test, and docs naming the owner and the key-name refusal
This commit is contained in:
+1
-1
@@ -839,7 +839,7 @@ each value one writer would spread that knot across packages, behind forwarding
|
||||
every public method. The draw state, the grammar, `DataType`, what a proof knows of a
|
||||
value, the builtins, the reading of data files and a table's rows read no engine type, so
|
||||
each sits in a package under `internal/`, behind the import list `imports_test.go` checks.
|
||||
A table's rows reach the engine table owning them as a payload of a type parameter. Valid
|
||||
A table's rows reach the engine table owning them as their owner, a value of a type parameter. Valid
|
||||
until `todo.md` item 107 moves the engine.
|
||||
|
||||
## Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape
|
||||
|
||||
Reference in New Issue
Block a user