Name the loop's own flag, and drop droppedWhileDraining()

2026-09-28 21:27:00 +02:00
parent cce1d7c02e
commit 2152b995d4
4 changed files with 8 additions and 10 deletions
@@ -768,6 +768,8 @@ rule and an index of the titles below.
  is how the first cut ended up answering the same question two different ways at admit and at
  release. Every other collaborator reads whether the link lives from it and keeps no copy: five
  copies held in step by statement order were what the 2026-09-28 comprehension runs ranked hardest.
+  `ReconnectLoop.halted` is the loop's own, for its timer, because `client()` also runs a loop with
+  no session behind it for `fromStart`; a session's loop is stopped by `Session.stop()` alone.
  The retry in `requestPastDrain()` asks `link.awaitsNextLink()` rather than `canCarry()`, which also
  reads the socket: a loop condition the link does not gate on spins against a link that admits it
  straight back.