A stop is to say whose it is from the frame that stopped

This commit is contained in:
Joseph Ferano 2026-09-25 10:15:47 +07:00
parent 9dd7dd4137
commit c1dcdeb5af

View File

@ -1517,7 +1517,8 @@ was delivered" is a generation number rather than a name, so evaluating from
inside a break into a thunk that stops on the same condition class is settled by
comparing two integers.
** TODO Whose break it is, which no counter answers
** NEXT Whose break it is, which no counter answers
Decided 2026-09-25: fix it. A stop records whether the thread that stopped was running the evaluation's thunk or the program's own code, so the sentence is decided by the frame and not by the generation counter.
A game loop that signals during the build or the wait bumps the generation exactly
as a thunk would. The machine-readable fields stay right; what is wrong is the
sentence. The per-frame program-or-eval label is computed by the daemon from