异常处理路径不是指异常，是指那些else。比如api gateway上面的大量建连-请求-不等请求结束断开连接，这种情况如何节约服务器资源。

再说说你说的这个。
协程本身是在用异步伪装成同步，提升开发效率和程序健壮性。不把抛出异常伪装成同步，后台开发显然会遇到子协程一进去崩溃而父协程在傻等的情况，在协程之前的开发太常见了

【 在 hgoldfish 的大作中提到: 】
: 协程本身是一个异步的流程。异常本来就不应该传递到父协程。你可以看看 python 协程和 js 协程也是一样的，子协程的异常不抛到父协程里面。
: go 本身的异常机制自身会处理好的。没问题的。
:
--
FROM 123.116.202.*

这个文章很好啊
不过在我看来，check是优化，确实不错

if err return
我喜欢这种explicit的错误处理方式，不够优雅，有点费劲，但非常简单。
【 在 hanjiamajia 的大作中提到: 】
:
: 还设计的好呢
: 设计的好，为什么要在 go2 里加check 关键字 https://github.com/golang/proposal/blob/master/design/go2draft-error-handling-overview.md
--
FROM 114.249.22.*

老黄历了吧，后来Linus好像也修正了自己的观点，而且C++最近10年的进化是非常显著的，现在学习C++的人是幸福的。
【 在 hgoldfish 的大作中提到: 】
: "LOL," was his response. "C++ solves _none_ of the C issues, and only makes things worse. It really is a crap language.
: "For people who don't like C, go to a language that actually offers you something worthwhile. Like languages with memory safety and [which] can avoid some of the dangers of C, or languages that have internal GC [garbage collection] support and make memory management easier.
: "C++ solves all the wrong problems, and anybody who says 'rewrite the kernel in C++' is too ignorant to even know that."
: ...................
--
FROM 111.198.244.*

        final_action和finally这么基本的东西，到C++ 20了还没进标准库……
        真不知道标准库这帮人在想啥

【 在 hgoldfish (老鱼) 的大作中提到: 】
: "LOL," was his response. "C++ solves _none_ of the C issues, and only makes things worse. It really is a crap language.
: "For people who don't like C, go to a language that actually offers you something worthwhile. Like languages with memory safety and [which] can avoid some of the dangers of C, or languages that have internal GC [garbage collection] support and make m
: "C++ solves all the wrong problems, and anybody who says 'rewrite the kernel in C++' is too ignorant to even know that."
: ...................
--
FROM 59.109.219.*

转Java吧，C++不能靠蒙  
  
【 在 mopo () 的大作中提到: 】
: 俺不幸都做过，linux下的qt、gtk++，win下的win32、mfc、COM、少量managed c++
: 各种crash和模板error调试到怀疑人生
:
: 【 在 hgoldfish 的大作中提到: 】
--
FROM 59.148.127.*