Cool! On Wed, Jan 17, 2018 at 08:27 Ian Lance Taylor <i...@golang.org> wrote:
> On Wed, Jan 17, 2018 at 3:30 AM, Matt McClure > <matt...@matthewlmcclure.com> wrote: > > > > Hard to say until I read both. My original message is based on my > experience > > with other languages and their specs. > > The Go spec is intended to be as readable as possible. > > Ian > > > > On Wed, Jan 17, 2018 at 01:09 Ian Lance Taylor <i...@golang.org> wrote: > >> > >> On Tue, Jan 16, 2018 at 6:40 PM, <matt...@matthewlmcclure.com> wrote: > >> > > >> > 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? > >> > >> I think so. Do you disagree? > >> > >> Ian > > > > -- > > http://matthewlmcclure.com/ > > +1 617 329 1189 > -- http://matthewlmcclure.com/ +1 617 329 1189 -- 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.
