You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gui: a wait for quiet called off on its way does nothing when it arrives
The window's clock hands what it fires to the toolkit's queue
(desktop.Later, time.AfterFunc then fyne.Do), and calling it off stops the
timer, not a call already queued. If somebody typed in that gap, the quiet
they broke still ran: it gave memory back twelve seconds later, in the
middle of their work, and took the place of the new quiet's handle, so
closing the window could no longer call that one off. tidy now counts the
waits called off and each call checks it is still its own - the same as
busy.epoch.
The concurrency guard reported a declared file that runs nothing, but only
among the files the walk reaches. A declared file that is gone kept its
declaration and its place on the race job's list, green. The check is a
function asked of a folder made in the test.
The changelog said memory goes back after the last thing done in the
window. It is the last setting changed or press of Preview or Generate -
scrolling does not count - and it waits while work runs.
Guards: TestAWaitCalledOffOnItsWayDoesNothingWhenItArrives (red on the old
tidy.go, 2 waits and 2 releases), TestADeclarationWhoseFileIsGoneIsReported.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments