Skip to content

own spec §35: drop the ternary-const leak note, fixed by #673 #674

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ASDAlexander77 merged 1 commit into from
Oct 23, 2026
Merged

own spec §35: drop the ternary-const leak note, fixed by #673 #674

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions tslang/docs/superpowers/specs/2026-09-24-own-memory-model-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4368,6 +4368,3 @@ Not here:
are not values `movesOf` checks, so `each`'s `ts.RetainSlot` is still `merged from several
branches` (and `moved inside a loop`). A `const each` of the same reads compiled before this section
and still does.
- Under rc a folded `const` that a ternary yields is never given back (`releaseDiscardedTemporaries`
skips a value a `ts.Result` uses), so the class cases leak `h` and `h2` under rc, and under own
too. The interface cases do not: their `ts.New` is used by the view, not by the branch.
Loading