3 ms·
I'm speaking mostly in terms of recoverable errors where it jumps to a logging section, carries on, but leaks memory.
by jstewartmobile 10y ago
I'm speaking mostly in terms of recoverable errors where it jumps to a logging section, carries on, but leaks memory.
- Manishearth 10y agoYou'd generally use Result<T> for recoverable errors (which won't have any destructor issues), but in some cases you might put a panic::recover at the event loop level (never seen this being done before, but I can imagine it happening) which catches the panic (only calling destructors up to the catch point -- this is done by the unwind mechanism) and moving on to the next event in the loop.