4 ms·
Well, in the actual package name, you can't include hyphens. I presume they're talking, then, about the directory name, which would have to differ from the act
by NateDad 12y ago
Well, in the actual package name, you can't include hyphens. I presume they're talking, then, about the directory name, which would have to differ from the actual package name, and that's a no-no. Their reasoning may be wrong, but the rule is still correct.
- 4mnt 12y agoDo you mean a directory name cannot contain a hyphen (-)? Or perhaps you did mean a slash (/)? I have never heard nor encountered about a package manager or filesystem that does not allow the use of hyphens.
- NateDad 12y agoThe Go package name, which is potentially different than the manner if the directory it resides in. Go package names badly include hyphens (only Unicode letters)
- NateDad 12y agoArg, stupid phone. Should say: The Go package name can be different than the name of the directory in which the package resides (although this is strongly discouraged). The directory may certainly contain hyphens, but the package name - the thing you see in the Go package foo statement - cannot contain hyphens... that's the actual package name, which can only contain unicode alpha-numerics.
- stephenr 12y agoPackage for what? It doesn't specify a particular type of package its "rules" are meant for.
- stephenr 12y agoRight so its only by going to the Github repo and looking through the readme that I discovered > tells if your idea for a Go package name is shit and yet nowhere else does it mention about being Go specific.