lainio / err2 Goto Github PK

I get no stack traces as "invalid memory address or nil pointer dereference" is a valid error and gets wrapped by err2.Returnf, loosing stack trace and making this bug impossible to debug. Is that expected?

Hello Lainio,

Thanks so much for putting this library together! We've been using it for several months now in our project. It has made error handling much better :)

I see there is a new method "Handle" which automatically annotates the error with the method's name. This is really helpful! One thing I noticed was that it decamels the method name. It would be nice to preserve the original so that it can be easily searched for without having to reassemble it. In terms of readability it still suffers anyway because it ends up keeping the pointer notation, ie "(*my struct) my method: some error message".

Thoughts?

I have some general questions about how to use err2 and I don't want to junk up your issues with Go newbie questions. Perhaps you could enable GitHub Discussions or else add a "Getting Help" or "Community" section to the README.md where you could link to your preferred Q&A forum.

• in v0.9.40 noerr handler works if it's the last defer handler of the package err2, i.e. executed first during function return
• will be fixed in v0.9.41
• thanks for finding it, @shynome