DEV Community

ques0942
ques0942

Posted on

1

xerrors has less feature about trace's detail

This is feedback for Go 2 Proposal.
This is my opinion. if you has any opinions for proposals, please feedback your one.

The proposal of Go 2 Error Values is looks good to me. Inspection and printing feature is simple and ease to use. but not enough to read error stacktrace.
Some case(i faced when i used sentry), we want to read error stacktrace(ie. program counter, function name, line number...etc) to create structured error data. Implementation of this proposal("xerrors") provide Printer interface only which is used to print error.
This interface is focus on printing and formatting so we can't use it to read stacktrace. If i want to read stacktrace by using "xerrors", i must write dirty code.
If "xerrors" will reveals stacktrace or returns runtime.Frame, it will be very useful. so i support this idea.

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

Top comments (0)

👋 Kindness is contagious

Engage with a wealth of insights in this thoughtful article, valued within the supportive DEV Community. Coders of every background are welcome to join in and add to our collective wisdom.

A sincere "thank you" often brightens someone’s day. Share your gratitude in the comments below!

On DEV, the act of sharing knowledge eases our journey and fortifies our community ties. Found value in this? A quick thank you to the author can make a significant impact.

Okay