4 ms·
As someone who's not into real-time or zero-overhead, this is still interesting: Is it feasible to restrict exceptions to throwing a single simple "error code"
by YouAreGreat 8y ago
As someone who's not into real-time or zero-overhead, this is still interesting:
Is it feasible to restrict exceptions to throwing a single simple "error code" type without losing much of value?
- foota 8y agoIt still works fairly well for knowing whether something can be recovered from, but you do lose some context, which needs to be provided in other ways for things like debugging.
- renox 8y agoI wonder if it wouldn't be possible to have 'heisenberg exceptions': if an exception is caught, it's just a normal exception, but if it isn't caught then there is a core dump which means you get all the data you need to debug the issue.
- kjeetgill 8y agoThis is very similar to how go's panic/recover work. In Java an uncaught exception will kill just the thread (and usually log the stack trace in the process).