It strikes me as odd that Effective Go recommends reading the language 
specification first.

"This document gives tips for writing clear, idiomatic Go code. It augments 
the language specification, the Tour of Go, and How to Write Go Code, all 
of which you should read first."

Is that really good advice for Go learners?

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to