News for hackers. Stuff that matters.
Re:Working with Errors in Go 1.13 by barrkel on Saturday October 19, 2019 @08:04PM (#21301481)
How do you convince every other library that you might sandwich on your call stack to use your error library so your error data gets passed through correctly?
Re:Working with Errors in Go 1.13 by tptacek on Saturday October 19, 2019 @10:39PM (#21302026)
Well, at this point, don't you just wrap the error? Isn't that the point of this post?
Re:Working with Errors in Go 1.13 by barrkel on Sunday October 20, 2019 @05:16AM (#21303054)
And stack trace in the middle?
Re:Working with Errors in Go 1.13 by _ph_ on Sunday October 20, 2019 @03:58AM (#21302790)
The other library doesn't have to use your error library, it just needs to preserve your error when passing through. To make this a common practise, this proposal was made.