FAQ
The flag should be the other way around.

Most people who complain about shadowing are either new to the language or
don't understand block scoping. So why make it a flag to enable the check
when they wouldn't even to understand what the flag does without
researching it.

On the other hand if some one does use block scoping correctly, after
getting the warning he will look at the flags and promptly disable the
check.

If the goal is to protect people from their possible mistakes, don't hide
it from the people who are more likely to make those mistakes.

Just my two cents.
On Feb 20, 2013 8:18 AM, "Michael Jones" wrote:

that was my intention...
On Wed, Feb 20, 2013 at 2:17 AM, Jan Mercl wrote:

Yes, that's maybe a good approach.

-j

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
Michael T. Jones | Chief Technology Advocate | mtj@google.com | +1
650-335-5765

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

People

Translate

site design / logo © 2021 Grokbase