News for hackers. Stuff that matters.
Re:Declined Proposal: A built-in Go error check function, “try” by danielparks on Wednesday July 17, 2019 @02:53AM (#20457148)
> Literally the first non-trivial code I wrote in go… I knew exactly where and how things could fail and where things were failing just by looking at the code.

Could you give an example?

I think you’re talking about something different than what I’m understanding. One of the major frustrations I have with Go error handling is the lack of stack traces, which means I often have to modify code in order to find out where an error occurred.

I’m pretty sure that’s not what you’re talking about, though.

There are no comments on this comment yet.