<p>Golang compiler error is pretty annoying for debugging</p>
<hr/>**评论：**<br/><br/>shovelpost: <pre><p>Use <a href="https://godoc.org/golang.org/x/tools/cmd/goimports" rel="nofollow">goimports</a>. Annoyance begone.</p></pre>dlsniper: <pre><p>You can use <code>goimports</code> on save, via Settings | Tools | File Watchers | + | goimports. This will trigger <code>goimports</code> when you save the file.</p>
<p>The upcoming IDE version, 2018.1, now in EAP see <a href="https://blog.jetbrains.com/go/category/eap/" rel="nofollow">https://blog.jetbrains.com/go/category/eap/</a> , will feature an option to optimize imports on the fly so that saving the file won't be necessary anymore and you can enjoy modern Go editing in the IDE, see <a href="https://blog.jetbrains.com/go/2018/02/15/goland-2018-1-eap-3-move-refactoring-better-test-runner-go-build-quickdoc-and-more/" rel="nofollow">https://blog.jetbrains.com/go/2018/02/15/goland-2018-1-eap-3-move-refactoring-better-test-runner-go-build-quickdoc-and-more/</a>.</p>
<p>If you have any other questions feel free to ping me here, or open an issue on the tracker <a href="https://youtrack.jetbrains.com/issues/GO" rel="nofollow">https://youtrack.jetbrains.com/issues/GO</a></p></pre>marksteve4: <pre><p>This is great. thanks</p></pre>donja_crtica: <pre><p>As Visual Code user, I didn't realize something like this could be annoying </p></pre>dlsniper: <pre><p>I would like to invite you to try GoLand and see how much better life can be without having to save after every keystroke in order to have the code checked for errors. Each editor has their own strengths and weakness, what's important is that their users are productive with them.</p></pre>
