Idiomatic naming in Go is one of the hardest things to communicate. Everyone seems to bring the idioms from previous languages. Dave Cheney writes about "Lengthy bureaucratic names carry a low amount of signal compared to their weight on the page". Identifiers are not sentences or stand alone stories. They are the the basic building blocks for our code. We have all seen code infected by these names - long names leading to long lines of code, and verbose walls of dense text, repetitive and hard to read.
I always encourage people to read https://go.dev/doc/effective_go#names to study the Go standard library, and develop a feel of what Go code should read like. > > -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/2cd93f81-9ae1-4e49-890c-b2d383955febn%40googlegroups.com.
