3 ms·
How about this? :) { foo } catch { bar }
by jayd16 2y ago
How about this? :)
{ foo } catch { bar }
- nonethewiser 2y agoThis is probably the one that would anger Golangers the most lol
- jayd16 2y agoThey could even have typed error checking for different errors and an automatic return error syntax. { Foo } catch (err) {} catch (err2){} throw
- 9rx 2y agoAgreed. The reduction in boilerplate to route error conditions is what we really need, if we are going to add any special error concept. errors.Is/errors.As and the accompanying switch/if statements can quickly consume entire screens of code for all but the most simplest of failure cases and as a result it often sees developers become lazy and just return err instead.