In the abstract, I think I agree with you. But in reality, what I see is that go projects use far fewer packages than, say, programs in Java. Many go projects use one or two omnibus packages--principally, I expect, to avoid having to worry about circularity issues.

By forcing this design pattern on developers (something no other language does), I think the result has been overall worse code rather than better.

Perhaps a warning, rather than stop-the-compiler error would have been a better choice. Not sure.

Either way though, I wholly agree that the compiler gives too little information, which is curious because it knows the needed data and should easily be able to present it in a useful way.