Jae Kwon
Jae Kwon
@ebuchman, what's a good figure to include there?
Related proposed solution: https://github.com/pkg/errors/issues/144
@puellanivis > Without reflect you cannot pass an interface type for it to be tested again, so each and every attempt to assert against any interface would have to for-loop...
> “the preferred method is to use errors.Wrap(), not errors.WithMessage().” False. Is it by far the most common? Yes. But it is not the “preferred method”. errors.Wrap should only be...
@puellanivis I just found 4 existing issues actually related to the problem that this proposal fixes.
> False. If you are calling a package and you need to know the stacktrace at your point for debugging, you call Wrap, if not, you do not, then you...
> Yes, I am being sarcastic, because apparently you think I don’t know that a type switch can use interfaces. I showed you a type-switch on an interface, even pointed...
Thanks for moderating, Dave. Sorry for getting the convo heated, Cassondra. Many thanks to issue #144. I agree that full stacktraces are also nice, in addition to tracing. I've taken...
Ok, I just ran into this, but what I expected was to be able to do this: ```golang func (err *sdkError) Cause() error { if err.cause != nil { return...
@davecheney: > I would appreciate it if you can help me understand, on pkg#89, not this PR, your use case, and why this change is necessary, and could your requirement...