flag: Use camelCase instead of snake_case for local var...

flag: Use camelCase instead of snake_case for local variables

[gri, 2013-06-13 16:43:18]

I can't get excited about these - it's completely internal. We do have a
CamelCase recommendation (which makes sense for a consistent API naming scheme)
but nowhere is it written that we have to slavishly follow it everywhere.
Otherwise, the next think will be that go vet is asked to enforce it.

Leaving for r.

[Dominik Honnef, 2013-06-13 16:51:26]

Yeah, I can see how these changes might be perceived as going "over the top". My
main intention is to have one consistent style throughout the standard library.
For example archive/tar mixes both styles in the same package, where snake_case
was introduced by a 3rd party contribution.

But as I said, if it's not worth it, I won't bother with it.

[rog, 2013-06-13 17:11:22]

On 2013/06/13 16:51:26, Dominik Honnef wrote:
> Yeah, I can see how these changes might be perceived as going "over the top".
My
> main intention is to have one consistent style throughout the standard
library.
> For example archive/tar mixes both styles in the same package, where
snake_case
> was introduced by a 3rd party contribution.
> 
> But as I said, if it's not worth it, I won't bother with it.

i think it's worth fixing these as i think
it's worth passing cleanly through golint
when reasonable.