> Of course there also was a reason why try! was replaced with `?`: awkward nesting and chaining. Go would have the same problem. Thanks to tuple returns being

> Of course there also was a reason why try! was replaced with `?`: awkward nesting and chaining. Go would have the same problem. Thanks to tuple returns being a bolted-on afterthought on the language, Go already features awkward and cumbersome nesting and chaining!