Re: About Go, D module naming

[Phil Lavoie]

In this case, I am convinced that there is no use of having the 
"no accessibility but visibility" particularity, because I cannot 
find any reason for it to stay like that (feature/exploit wise). 
On the other hand, I don't work on the compiler and I have no 
idea of what difficulties in would imply to change this. So the 
question I guess would be if changing its behaviour to make it 
predictable justifies the cost/work, for now (priority wise)?