Go development workflow

[Tim K]

I see lots of tools being mentioned in various posts and blogs.

What is the recommended core of tools that someone in the early days of Go development should run?

* go fmt (or goimports?)
* go run|build|install -race (for race detection)
* go vet
* go lint
* ...

There is this list but I'm interested in the opinions of those with a bit of Go experience to name their core tools that are "must run".

I'm also a bit confused about "go fmt" vs gofmt, "go doc" vs. go doc, etc. Any good discussions on which form to run?

Tim

[andrey mirtchovski]

just send your code for review to any of the go forums list with a
note saying "please take a look". people will usually employ all the
necessary tools to bring it into conformity and in most cases will
point out the most egregious bugs or design mistakes.

[Robert Melton]

On Sun, Nov 22, 2015, at 19:57, Tim K wrote:

What is the recommended core of tools that someone in the early days of Go development should run?

 

A simple and sane way to do Go development is call goimports from your editor of choice on save, it will tidy up your code and imports.  Then setup and use https://github.com/alecthomas/gometalinter to roll together all the various lint and hygiene messages.  You can integrate gometalinter with your editor, or just use it from the console. 

 

Then just make sure to write and maintain your tests and you should be in a good place.  

 

--

Robert Melton | rme...@gmail.com

 

[Tim K]

"go crowdsource" tool?

[Giulio Iotti]

On Monday, November 23, 2015 at 3:42:50 AM UTC+2, Tim K wrote:

"go crowdsource" tool?

go nuts

-- 

Giulio Iotti 

[Micky]

On Tue, Nov 24, 2015 at 8:55 PM, Giulio Iotti <dullg...@gmail.com> wrote:

On Monday, November 23, 2015 at 3:42:50 AM UTC+2, Tim K wrote:

"go crowdsource" tool?

go nuts

go bazinga