Use of 'check' manifest const for error checking?

<p>Any gophers here approve of using something like a &#39;check&#39; macro that can be used to hide err checking spaghetti code?</p> <p>Example:</p> <p>#define check(err, call) { err = call; if (err) return err; }</p> <p>Usage:</p> <p>check(err, connect(context));</p> <hr/>**评论：**<br/><br/>bbrazil: <pre><p>Some libraries have a <a href="http://golang.org/pkg/text/template/#Must" rel="nofollow">Must function</a> or <a href="https://godoc.org/github.com/prometheus/client_golang/prometheus#MustRegister" rel="nofollow">variant</a> that panics if an error is returned.</p></pre>dchapes: <pre><p>Which of course are intended for use almost exclusively in global variable initializations and such. Just as with regular panics being abused where there should instead be error returns or clean exits (e.g. via <code>log.Fatal</code>) I&#39;ve seen these abused as well.</p></pre>tdewolff: <pre><p>To be honest, I don&#39;t have that many error-checking ifs throughout my code. I mean I do check every error, but it doesn&#39;t bother much when you properly structure your code. Anyways, most of my error checking statements are unique. Either in the error string or by handling other assets.</p> <p>However, for something like many sequential writes to an <code>io.Writer</code> I can understand why you would come up with this. But check <a href="https://talks.golang.org/2013/bestpractices.slide#5" rel="nofollow">https://talks.golang.org/2013/bestpractices.slide#5</a> for a solution.</p></pre>GoGoGadgetGopher: <pre><p>you can use context-sensitive code folding in your editor if you really hate looking at the error checking all the time</p></pre>