That is kind of a terrible name for that directory. It's confusing to use because the package name does not match the directory name. But I guess I can't think of a reason that the go tool should not support it.

CL https://golang.org/cl/20893 mentions this issue.

I agree with @minux there is already enough confusion around go build and go test supporting .go files vs the recommend use of packages. To allow the go tool to fetch a package that has a directory named something.go will just add more confusion to an area newcomers already find difficult.

The clincher for me is package something.go is not a valid package declaration, so the name of directory cannot match the packages' name.

I vote to close this as unfortunate.

@minux,

I don't get your concerns about go build with such paths. Can't go just check if the path is a file or a directory?

My package is not the only one I have found ending in .go. I can very well rename it to have the .golang suffix (or any other name) and avoid this issue. But what about the several packages out there with the same issue (and future ones that will run into it eventually)?

I agree that the name of the package is not good, but go tools failing inconsistently due to directories with the .go suffix without being noisy about it is worse imho.

Reference: gojp/goreportcard#90

What about adding info to the docs that directories should never end with .go and / or failing noisy when it happens for the know reasons?

Or, better yet, explaining that projects / package directories should always use valid package names...

Blocked on Code-Review Label
https://go-review.googlesource.com/#/c/20893/