Hacker News Reader

Repeating the package name is fine if it's exactly the same name (modulo capitalization) and there's nothing better to name the type anyway. The style issue would arise with e.g. uuid.UUIDVersion, which should just be named uuid.Version. There used to be a gopls lint that would flag names like uuid.UUID but it got relaxed awhile ago.

No. What else could it reasonably be named? Hard to imagine.

The rule has always been intended to cover types that have another word in them but still choose to pointlessly repeat the package name.

`uuid.UUIDGenerator` is a hypothetical example of the anti-pattern that would instead be better named as `uuid.Generator`.

> No. What else could it reasonably be named? Hard to imagine.

Ocaml often just has it be T

so uuid.T

uuid.Entifier

Yeah, I would have gone with uuid.V4 or something. But oh well, as long as it works. :D

V4 or V7 are just how you initialize them (constructor), but then this the same representation, so they don't need specific types.

That's why we called ours uu.ID

https://pkg.go.dev/github.com/domonda/go-types@v0.0.0-202607...