The Go policy not to generate ANY warnings is now deeply rooted, it is not going to be changed this late in the game, not even if one or more instances could justify the break with tradition.
The go vet tool will help you discover situations where the code is conventionally ambiguous or even broken, but I'm not sure it would apply here, as Go also supplies defaults for all "uninitalised" values. But I doubt you'll repeat your mistake any time soon. Eventually, you'll also grow to appreciate the wisdom in treating "warnings" as either too serious to complete compilation or too trivial to report. Lucio. -- 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.
