Why custom types instead of primitives? about upspin HOT 2 CLOSED

I believe the reasoning is that custom types solve a set of problems, from the developer's perspective.
Yet you can say that that is what the argument name is for, but this will be matched by the compiler.

Also I encourage you to read @robpike blog post on the errors package used in this project.

The Path and User fields denote the path and user affected by the operation. Note that these are both strings, but have distinct types in Upspin to clarify their usage and to allow the type system to catch certain classes of programming errors.

From https://commandcenter.blogspot.com/2017/12/error-handling-in-upspin.html

from upspin.

@bundgaard is correct, it's for the errors package and it works great.

from upspin.