4 ms·

To their credit, the Go team withdrew most of Error Values draft 2 [1] after a great deal of negative feedback. However, they've kept one unpopular change to fm

To their credit, the Go team withdrew most of Error Values draft 2 [1] after a great deal of negative feedback. However, they've kept one unpopular change to fmt.Errorf(). We can hope that draft 2 of Error Handling [2] won't look anything like draft 1, for reasons such as [3]. [1] https://github.com/golang/go/issues/29934 https://github.com/golang/go/issues/29934 [2] https://github.com/golang/go/wiki/Go2ErrorHandlingFeedback https://github.com/golang/go/wiki/Go2ErrorHandlingFeedback [3] https://medium.com/@mnmnotmail/golang-how-dare-you-handle-my-checks-d5485f991289 https://medium.com/@mnmnotmail/golang-how-dare-you-handle-my...

ra7 7y ago
From [1]: > The most contentious point of the original design was the special-case handling of a trailing ": %v", ": %s", and ": %w" in the format string, which did not follow the usual printf model in which the meaning of % verbs is context-independent and all non-% text has no meaning at all. We will remove those special cases from Go 1.13. At least, they removed the really ugly special cases! [1] https://github.com/golang/go/issues/29934#issuecomment-489682919 https://github.com/golang/go/issues/29934#issuecomment-48968...