feat(base): 0.R4 - a queue keeps its own count, so every package verb takes only its own state; ludic migrate state --prune
ludic.base's Queue<T> carries a QueueTag (its name and pending count): queue_new(name), q_push(q, v), q_drain(q), q_clear(q) take no BaseState, and core_undrained(tags) names the given queues still holding facts. A reducer on a package's state can now call that package's verbs (wallet_earn(wallet_st, n)). ludic migrate state --prune (ludicc --migrate-prune) takes out each state parameter a function no longer uses, nor anything it calls, and the argument that fills it - including an argument for a parameter the callee has dropped, which is taken out before the call is checked, so a generic's T is told by the argument that says it. A reducer keeps its state. --dry-run now counts the edits it would make. Every package was moved with it: 608 base_st parameters and their arguments, 1889 edits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
8cf4b3fed6
commit
71735b10a2
151 changed files with 58668 additions and 54719 deletions
14
LANGUAGE.md
14
LANGUAGE.md
|
|
@ -274,7 +274,7 @@ counter.ludic:5: error: this assignment: LIMITS is module-level and immutable al
|
|||
counter.ludic:3: error: x: mut int - mut is for a state parameter, and int is not a state
|
||||
```
|
||||
|
||||
**`ludic migrate state [file|dir...] [--runtime] [--dry-run]` moves programs there.** It compiles
|
||||
**`ludic migrate state [file|dir...] [--prune] [--runtime] [--dry-run]` moves programs there.** It compiles
|
||||
each program and, from the compiler's own view of every name:
|
||||
|
||||
1. a var nothing writes, holding a value (an int, a string, an enum...), becomes a module-level
|
||||
|
|
@ -314,6 +314,18 @@ ludic migrate state packages <every example program> packages/ludic.lab/example/
|
|||
migrate: 1804 vars into 126 states, 64 into lets; 23498 edits in 460 files
|
||||
```
|
||||
|
||||
**`--prune` takes out what a function no longer uses:** each state parameter that neither the
|
||||
function nor anything it calls uses, and the argument that fills it at every call. An argument for a
|
||||
parameter the callee no longer has goes too - a package's verb that dropped a state leaves its callers
|
||||
passing one too many, and `ludic migrate state --prune <program>` puts them right. A reducer keeps its
|
||||
state. When ludic.base's queues began keeping their own counts, every package verb lost its
|
||||
`base_st` this way (`wallet_earn(wallet_st, n)`, not `wallet_earn(base_st, wallet_st, n)`):
|
||||
|
||||
```
|
||||
ludic migrate state --prune packages packages/ludic.lab/example/plate.ludic
|
||||
migrate: 0 vars into 0 states, 0 into lets; 1889 edits in 132 files
|
||||
```
|
||||
|
||||
### Actions and reducers (`action`, `reducer`, `dispatch`)
|
||||
|
||||
Threading states makes a function's signature say what it touches, and it shows where one function
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue