[Twey]

All recurrent people problems are system problems.

[microgpt]

As seen by the fact that forcing the programmer to write let _ = to silence the warning did not fix the bug.

You know what might've solved this though? Using threads instead of async

[Twey]

I think that's more of a workaround than a fix. Relying on unstructured concurrency does mean you no longer have to understand the scheduling of your program's fibres (… until you do), but it introduces a bunch of new footguns around things like correct cancellation, error propagation, and predicting resource lifetimes.