> I don't think that specific line of code you linked is problematic I highlighted the line as an example of one of many lines in that code where exceptions are raised, but are not caught. Not catching them leads to leaks and/or crashes because of missing exception handlers / defer / whatever your preferred handling mechanism is. If that is not problematic, I'm not sure what is.
> when you call asyncCheck you're asking for your process to crash No, you ask that the exception is transferred to the function calling `runForever` where it can be caught - this is a design issue with `asyncCheck` which leads to poor error handling at best, and like you say, crashes at worst. Whether that's fine or not of course depends on your use case, I guess.
