You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two things which prevent this package from being go get compatible and idiomatic. The first can be fixed with a pull request, but the second requires changing the repository name/location.
Go projects use a single directory for all files in a package, and this directory generally has the same name as the package name (so src directories aren't used in Go projects).
However, project names that end in .go are no longer recognized by the entire Go toolchain, which means that the project name should really be underscore (or perhaps __, not `underscore.go).
(I was going to submit a pull request, but then I realized that the respository name ended in .go, which ideally should be fixed before moving the files out of the src directory; doing this in the other order would result in an inconsistent intermediate state.)
The text was updated successfully, but these errors were encountered:
There are two things which prevent this package from being
go get
compatible and idiomatic. The first can be fixed with a pull request, but the second requires changing the repository name/location.Go projects use a single directory for all files in a package, and this directory generally has the same name as the package name (so
src
directories aren't used in Go projects).However, project names that end in
.go
are no longer recognized by the entire Go toolchain, which means that the project name should really beunderscore
(or perhaps__
, not `underscore.go).(I was going to submit a pull request, but then I realized that the respository name ended in
.go
, which ideally should be fixed before moving the files out of thesrc
directory; doing this in the other order would result in an inconsistent intermediate state.)The text was updated successfully, but these errors were encountered: