While theoretically, I agree with your argument against using the short variable declaration pattern, I've personally found that in practice it isn't an issue. I think that if this is something you run into often, it might suggest that you're letting too many variables into your scope, whether that means having too many generically named global variables or being inside too large a function.
On Fri, Jan 27, 2017, 11:57 AM Shawn Milochik <shawn.m...@gmail.com> wrote: > Here's a good discussion about it: > > https://groups.google.com/d/msg/golang-nuts/J9QeizedpuI/ECifbR0YGcsJ > > TL;DR: scope > > -- > 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. > -- 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.
