Personally, I feel that the motivation for the issue is one of convenience. The most common use case is changing the flow control in the event of an error to re

Personally, I feel that the motivation for the issue is one of convenience. The most common use case is changing the flow control in the event of an error to return from the current stack. I'm not a fan of defining an error handler. This seems far too intrusive and cumbersome and a bridge too far. GoLand gets around this somewhat by adding in the Live Template of "err" being a macro expansion for the if err != nil { return }. However, it still adds those 3 lines below each requisite call. If they added a new keyword that took the place of this macro, would that be too intrusive? Clearly, this only works if you have named return values. It would be nice if there was a bash/Ruby-like chaining, such as: var1, var2, var3, err := call1(args) && var4, var5, var6, err := call2(args) && ... and more calls and so on ... return callN(args) Where "&&" would perform the if err != nil { return } in-line. Should the first call return a non-nil error as the last argument, flow would be returned to the caller. If not, the flow continues as normal. This could even be extended in the case of function chaining: return call3( call2( call1(args) && ) && ) The downside of using && is that it's overloading the && and may cause some compiler/developer confusion. This was just an example based on a familiar use case (bash); another token can be used. Rasky suggested something like this based on another proposal in the thread, but using "?" instead. Another way to approach this might be an overlay language analogous to Kotlin. There could be a Go dialect that compiled into Go that provided this feature. Or, possibly an optional "plugin" for go's compiler that added an intermediate transformation step prior to compilation based on new keywords, but this will frustrate debugging and lead to other surprises. Generators tried to do this, but it doesn't seem to have taken off, from the repos I've read. Just my 2c