[go-nuts] Re: golang compiler warning idea

2018-01-31 Thread matthewjuran
Here's a proposal covering this: https://github.com/golang/go/issues/21114 Matt On Wednesday, January 31, 2018 at 2:58:15 AM UTC-6, Egon wrote: > > Use govet and see https://golang.org/cmd/vet/#hdr-Shadowed_variables... > Of course, there are more tools that can help you > https://github.com/al

[go-nuts] Re: golang compiler warning idea

2018-01-31 Thread Egon
Use govet and see https://golang.org/cmd/vet/#hdr-Shadowed_variables... Of course, there are more tools that can help you https://github.com/alecthomas/gometalinter + Egon On Wednesday, 31 January 2018 02:05:57 UTC+2, Jacob Lancaster wrote: > > So, I'm new to Go, but I wanted to make a cli app

[go-nuts] Re: golang compiler warning idea

2018-01-30 Thread Lucio
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 br

[go-nuts] Re: golang compiler warning idea

2018-01-30 Thread Jacob Lancaster
One of my roommates pointed out that this shouldn't throw a warning or error because I didn't assign a value to the variable, but it should be a warning because I hide the scope of the original text variable with the text variable inside the loop scope. The C# compiler throws a warning for a ve