What’s the best argument to made made in favor of ... untyped errors in strongly typed languages?
-
Empirically, Java tried it and programmers did everything in their power to squirm out from it
Yeah but I don't think that was a fault of typed errors, it was a fault of how their type system interacted with it. If an interface let implementors state what errors they could return, that would fix most of the issues. TBH I don't know how to make it work well with inheritance
-
-
I think the biggest thing that Rust folks have zeroed in and agreed on is that typing is more important for libraries than applications. Libraries should return enums of their errors and give applications a chance to recover, apps usually just need a `Box<dyn Error>`
-
Interesting, I would've expected the opposite. Libraries returning enums of their errors means they can never grow new errors without breaking clients
- 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.