Go2ErrorValuesFeedback

Go 2 Error Values Feedback

This page is meant to collect and organize feedback about the Go 2 error values draft designs.

Please post feedback on your blog, Medium, GitHub Gists, mailing lists, Google Docs, etc. And then please link it here.

As the amount of feedback grows, please feel free to organize this page by specific kind of feedback.

Error Inspection

• Greg Weber, “Horizontal composition: Error inspection for groups”, September 2018
  • Eyal Posener, "Reply", September 2018
• K. Alex mills, "Rename Wrapper to Unwrapper", September 2018
• jimmy frasche, "Why limit this inspection to errors?", August 2018
• Dan Kortschak, Carrying contract expectations and values causing errors in ev3go, August 2018
• Daniel Theophanes, "Go 2 Design: Error Inspection with Error Lists, August 2018
• Cosmos Nicolaou "Inspection of errors in a different address space", September 2018
• Chris Siebenmann, "Error inspection improves current annoyances but may not go far enough", September 2018
• Paul Meyer, “[errors.New?]( - Your Name, “Title”, August 2018
• Vojtech Vitek "adopt Cause and Wrap from github.com/pkg/errors", May 2018
• Your Name, “Title”, month year
• etc.

Error Printing

• Calle Pettersson, Multi-line errors and log collection tools”, August 2018
• jimmy frasche, "Why limit these interfaces to errors?" , August 2018
• Chris Hines, “Types cannot implement both the errors.Formatter and fmt.Formatter interfaces ”, August 2018
• Dean Bassett, “Make errors.Detailer, not errors.Formatter”, September 2018
• Your Name, “Title”, month year
• etc.

Misc

• Andrew Chambers, My current error approach, August, 2018
• mikioh, A walkthrough on Error Values for Issue 18183, October, 2018