From c1dcdeb5aff387fe3cce7e3b4cbae161ea03e56d Mon Sep 17 00:00:00 2001 From: Joseph Ferano Date: Fri, 25 Sep 2026 10:15:47 +0700 Subject: [PATCH] A stop is to say whose it is from the frame that stopped --- TODO.org | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/TODO.org b/TODO.org index 83afb571..cb5b1090 100644 --- a/TODO.org +++ b/TODO.org @@ -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