Re:Declined Proposal: A built-in Go error check function, “try”
by gridlockd on Thursday July 18, 2019 @04:55AM
(#20468005)
The context here is Java's checked exceptions, which have to be handled explicitly at the site where they may occur, leading to control flow that - in my view - isn't substantially different from handling errors with if/else.
Re:Declined Proposal: A built-in Go error check function, “try”
by ScottFree on Thursday July 18, 2019 @08:06AM
(#20468895)
Fair enough.
Re:Declined Proposal: A built-in Go error check function, “try”
by wvenable on Wednesday July 17, 2019 @12:52PM
(#20461494)
I don't understand the argument that stack unwinding is unpredictable -- the most naive implementation of exceptions would just be multiple-function returns with automatic propagation (effectively the same as automatically putting the try! macro on every call in Rust).
Nothing about try/catch is like a "roaming goto".
http://www.lighterra.com/papers/exceptionsharmful/