3 ms·
Exceptions are worse than go-to, they're a comes-from statement. At least with a go-to you know where you're going when you look at it -- with exceptions you co
by arcticbull 6y ago
Exceptions are worse than go-to, they're a comes-from statement. At least with a go-to you know where you're going when you look at it -- with exceptions you could be coming from literally anywhere. All sorts of different control flows all filter into this one weird spot.
Exceptions are probably the worst thing in computer science.
This is a hill I'm happy to join AprilArcus on.
- CyberRabbi 6y ago> exceptions you could be coming from literally anywhere. False. exceptions can only come from throw statements, which are both static and finite within every codebase. > Exceptions are probably the worst thing in computer science. Opinion, irrelevant.
- arcticbull 6y ago> False. exceptions can only come from throw statements, which are both static and finite within every codebase. Not between libraries and library customers. From the perspective of the library author, the set is dynamic and uncountable, and similarly from the perspective of the library customer, any exceptions thrown are dynamic and uncountable. > Opinion, irrelevant. It's almost like opinions come from some basis worth exploring instead of outright rejecting without consideration. In my (obviously irrelevant) opinion, you may grow as a person if you learn to explore the opinions of others :)
- monadic2 6y agoThat's ridiculous, exceptions always come from further down the stack and can whose throw location can be precisely identified with basic debug symbols.
- arcticbull 6y agoIndeed, and that is orders of magnitude harder to reason about than something that can only come from a specific invocation.
- deleted 6y ago[deleted]