I don't think you are creating any drama to be honest. I understand how frustrating it must be.
replyThere is a similar issue in kotlin where a cancellation is marked via a CancellationException but that extends IllegalStateException and thus Exception. Because of that it gets caught and swallowed all the time. This is a constant source of bugs for me at work and google has resorted to a bunch of linting to get around this design mistake.
The most frustrating part about it for me it's Andrew's argument: just write correct code. I have C at home.
replydeleted
replyIn the future, tooling can run those checks statically on IR.
replyUnfortunately, it you want to handle errors right, it's overly verbose, so no one really does it. That's my problem really. Even in the blog post snippet, I could have show well behaved code, because I'm well aware of it, but then the error handling would be more code than the part I'm trying to showcase. Static analysis will not help there.
replyIn the future, it would be good to not need to require that unwritten tooling
reply