@niclas it's "Go" ;)
also: *sad gopher noises
@bonifartius Yeah, right... Good luck when googling "go" and generic programming terms, and that is part of the problem with it. Perhaps Google/Azure/DuckDuckGo have learned that you mean "go language" when you write "go" but I get random stuff. It is even worse than "C" when it comes to searching.
@niclas i search for golang too, but that's just to accommodate the search engines. i remember the times where "python" would give you the actual snake as first result ;)
@bonifartius But, it is not my main complaint. It is that it is too easy to make silent mistakes, especially with reference operator (or whatever you call it - "*"). Forget that in one place and compiler is happy to make copies of your structs and 100,000 instructions later have a nil, and one goes "Huh???"
@niclas maybe try "go vet" and "golint", those are pretty good at catching stuff which is commonly a mistake.
i'm not really sure what error you mean without code, if it makes copies of your struct because it isn't a pointer you can't have nil as value. nil can only happen with pointers, slices, maps and interfaces.
@bonifartius All in all, GO feels like a big step backwards, when it comes to syntax and memory model abstraction.