About Go, D module naming

[bearophile]

Peter Alexander:

> This is a tricky one. On one hand, it *is* a useful way to 
> catch errors, but on the other it's a constant source of 
> irritation when you are tinkering with code during 
> development/debugging.

I agree. I think a simple way to solve this problem is to put 
"unused variables" among the warnings. So when you are tinkering 
with code you don't use -wi, if you want.

-------------

eles:

> However, it is reasonable to include something like strictness
> levels as part of the compiler? (think gcc with MISRA-C
> integrated).

I think this to implement that there is a lot of work to do.

D tries to improve over C/C++ regarding static code safety, but 
there's a good way to go still (recently I have written a small 
article on this).

Bye,
bearophile