Dave Cheney

I see what you are asking for, the logic for "always capture a stack trace unless one already exists" sounds complex to implement, and hard to document, but I'll think...

> wouldn't give me the desired error output since all of the WithMessage output is appended to the bottom of the stack trace. This only happens with `%+v`. With `%v`...

> What's the reasoning behind separating out the message at the bottom? What do you consider the right way to do this? This looks like a bug, @noonat please open...

TL;dr - yes, that's not a thing I want to add. The goal of this package is simplicity. That comes via having the fewest ways to do things, which itself...

Hi. You’ve given me no information about how I can help you solve your problem. Which version of Go? Which operating system? What commands did you type, show all of...

I tried to add some CI around this and from what I can tell, because the openbsd bindings use CGO it is difficult to cross compile them. I think this...

Thanks for the detail. I don’t know how to fix this as cross compiling cgo code is fraught with difficulty

@gdamore i sent you an invite to this repo so I won’t be a blocker any more

@jaekwon @puellanivis time for a time out please. Please revisit this discussion in the new year once you’ve calmed down. Thank you

How does using this package make the original stack trace unavailable. The goal of this package is to preserve the original error.