Stefan Haller f9b790a1f9 Let OnUIThreadAndWait's error be about the wait, not about f ... Every caller passes an f that unconditionally returns nil, so f's error return has never carried anything: the value is dead weight, and it occupies the one channel the wait itself needs to report that it couldn't run f at all. Drop it, so that the error the wait returns can only ever mean that. Work that can fail hands its error back through a captured variable, the way the background fetch already hands back four values, which keeps the two outcomes distinguishable at a call site that has both. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-08-12 11:04:53 +02:00
..
async_handler.go	Copy gocui files into lazygit repo under pkg/gocui	2026-04-30 14:29:08 +02:00
async_handler_test.go	Copy gocui files into lazygit repo under pkg/gocui	2026-04-30 14:29:08 +02:00
tasks.go	Let OnUIThreadAndWait's error be about the wait, not about f	2026-08-12 11:04:53 +02:00
tasks_test.go	Let OnUIThreadAndWait's error be about the wait, not about f	2026-08-12 11:04:53 +02:00