On 2020-09-28 23:28, Ian Lance Taylor wrote: > I don't think there is any one solution that will be used in all > cases. Where the standard library can reasonably provide a shared > error type, it should, as it already does for types like os.PathError > and os.SyscallError. For a user package, whether it returns a > specific error type is part of that package's API. Often there is no > need for special error types for a user package. Where there is a > need, the error types should be documented like any other part of the > API
Is ENETUNREACH - "network is unreachable" typed anywhere? I assume string matching on these is part of the Go 1 promise? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1f29dfd6-2f41-ac84-6ee8-c9ff0d4bf917%40gmail.com.
