* John Souvestre <j...@souvestre.com> [170222 11:16]: > Ø does it sounds good to disable (in specs) named return vars shadowing ? > > This would help,
I don't think this is a good solution. It also breaks Go 1 compatibility. > but the := problem isn’t limited to return variables. > I think that it’s when there are two (or more) variables, and only one > is new, that is the real flaw. I would prefer that it only work when > both variables are new. This I agree with 100%. > I’ve taken to never using := in any multiple variable situation to > avoid the problem. This is something that a ver or lint utility can > check for now, too. J Me too. In fact, I try to only use := in if/for/switch, since I can't use var there. As a separate statement, it's easy to use var ... = instead of ... :=. ...Marvin -- 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.
