On Wed, Nov 13, 2024 at 1:28 PM ben...@gmail.com <benh...@gmail.com> wrote: > > > Personally I mostly think that is OK. One of the guidelines that Go > > follows is to encourage people to write code rather than write types. > > To me this falls into writing types. > > > I'm intrigued by this concept, but I don't really know what it means. I've > seen your (Ian's) similar comments at > https://go.dev/blog/when-generics#write-code and > https://github.com/golang/go/issues/29649#issuecomment-454820179 about the > "general guideline for programming Go: write Go programs by writing code, not > by defining types". > > But can you flesh that out a bit, or -- even better -- point to some examples > of what you do (and don't) mean? Or is there some "further reading" on the > subject you can link to? > > Does it simply mean to start by writing functions and imperative code, and > worry about the types/structs as they come up?
Essentially, yes. I think Rob Pike explains the idea well in https://commandcenter.blogspot.com/2012/06/less-is-exponentially-more.html. Ian -- 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. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcWK_umiG7UXx0ZZQG3zYJ6zKfTjbHOmc7vo5qQ0_ZUKdg%40mail.gmail.com.
