Go 语言最新的 errors 包给出了 %w 的方式,而不是 github.com/pkg/errors 这个包
2021-04-01
1
4
Marvichov
> There is one significant drawback to this approach, at least for some applications: there is no way to know how much of the processing completed before the error occurred. If that information is important, a more fine-grained approach is necessary. Often, though, an all-or-nothing check at the end is sufficient.
感觉应该加进`Error Check Hell` section. 不像exception, 你可以知道错在哪一步, this approach honors **all-or-nothing**
2021-04-18
Marvichov
nvm, the end of rob pike's article:
> Finally, for the full story of my interaction with @jxck_, including a little video he recorded, visit his blog.
2021-04-18
Marvichov
`Golang Error Handling lesson by Rob Pike` (http://jxck.hatenablog.com/entry/golang-error-handling-lesson-by-rob-pike) 的链接里面是日文的. 正确的链接应该是第二个reference的链接?