What is the philosophy in golang error? I also saw a lot of packages 
have their own Error override error interface. Why there is no shared Error 
structure with a shareable error code?

在 2017年8月2日星期三 UTC-7上午11:36:11,yihao yang写道:
>
> Hi,
>
> I found it is very difficult to judge an error in golang. For example, if 
> I want to judge a specific error returned by a function, but sometimes the 
> error is just newed by errors.New(xxx).
> In those situations, should I just compare the error string to know what's 
> the exact error? Is that a go-way to do so? I'm a little confused.
>
> Thanks,
> Yihao
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to