ludic/changes/prune-late-states.md
Orkuncakilkaya c35481f344 fix(migrate): 0.R4 - --prune keeps a state declared after a plain parameter; a parameter named twice is refused
On Maroon Lake the prune gave home_keep_records(base_app_st, home_st, r: RunRecords, save_app_st) a
second save_app_st at the front, and every call a second argument: a state declared after a plain
parameter was not counted as declared. It is now, and a call to such a function is never given the
state again. `ludic build --check` let the duplicate through and clang refused it; the checker now
refuses a function that names two parameters alike (`add names two parameters n`).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 05:32:08 +03:00

8 lines
576 B
Markdown

bump: patch
type: fix
**`ludic migrate state --prune` keeps a state declared after a plain parameter, and a parameter named twice is refused.**
A function like `home_keep(r: Records, save_st: mut Save)` was taken to lack `save_st`, and the
prune gave it a second one at the front (`home_keep(save_st: mut Save, r: Records, save_st: mut
Save)`) - which `ludic build --check` let through and clang then refused. The migration now counts a
state anywhere in the list as declared, and the checker refuses a function that names two parameters
alike (`add names two parameters n`).