Yeah, this is a great description of how our errors package helps a lot. You can tie user-facing status codes and messages to errors with stack traces, and only

Yeah, this is a great description of how our errors package helps a lot. You can tie user-facing status codes and messages to errors with stack traces, and only show the user-specific message to end users. Moreover, since you can bind arbitrary values to error types with our error library, internationalization is easy. Instead of binding a string user message, you can bind a locale->string map user message