sorry, i cant find your posts by asking my friend google, not reading your signature.
would you be kinder than me to post their urls so i can figure out how you consider few cases ? thank you. On Wednesday, July 3, 2019 at 4:14:19 PM UTC+2, Robert Engels wrote: > > The two posts I made regarding the errors as values blog clearly > demonstrates the significant problems with the current approach. > > On Jul 3, 2019, at 8:23 AM, mh cbon <mhh...@gmail.com <javascript:>> > wrote: > > but exceptions are shit. even the typed catch/final statements are a > workaround. > > On Sunday, June 30, 2019 at 7:03:49 PM UTC+2, Robert Engels wrote: >> >> I think both of the proposals are fine, but they suffer from the “lack of >> completeness”. In that, they improve things, but don’t go far enough so the >> incremental benefit is not high enough. A key component of exceptions is >> the concept of ‘throws’ which is both self documenting, and requires >> handling, which enables flow analysis (manual and automated). These >> proposals don’t supply this functionality. They also don’t cover automatic >> stack capture, which is essential in diagnosing problems in large, complex >> systems. >> >> On Jun 30, 2019, at 11:04 AM, Liam <networ...@gmail.com> wrote: >> >> If you really care to "catch" errors, you want this: >> https://github.com/golang/go/issues/27519 >> >> If all you need is to allocate a line to check an error and take an >> action, you want this: >> https://github.com/golang/go/issues/32611 >> >> But it's all moot. the Go team has told us we must prove that try is >> inadequate for existing Go projects, and altho that can be proved, it won't >> be clear for a couple years until use of Error Values propagates. >> >> On Thursday, June 27, 2019 at 11:44:23 AM UTC-7, Nate Finch wrote: >>> >>> I really don't like the try proposal >>> <https://github.com/golang/go/issues/32437>, because I think it hurts >>> readabiity of the code. But I think the fix is not too hard, so I made a >>> counter proposal, catch: >>> >>> https://github.com/golang/go/issues/32811 >>> >>> Catch works just like try, except it has to be a statement and has to be >>> passed an error explicitly, rather than returning arguments to the left >>> hand side. This make the conversion of old code to new code look a lot >>> more like normal go code. >>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golan...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/68e3407a-57cc-42f2-8819-7c0369f5ca4b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/golang-nuts/68e3407a-57cc-42f2-8819-7c0369f5ca4b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golan...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/e706cd96-1a07-4d02-a92c-a13538e17388%40googlegroups.com > > <https://groups.google.com/d/msgid/golang-nuts/e706cd96-1a07-4d02-a92c-a13538e17388%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/ba702909-0fdd-4f93-ae20-2bc2fdf91c56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
