News for hackers. Stuff that matters.
Re:Go 1.19 Beta 1 is released by erik_seaberg on Saturday June 11, 2022 @03:10AM (#31702604)
if err != nil is continuously painful. f(g(), h()) with error handling takes nine lines, maybe twelve? Everybody has to use Errorf() everywhere or nobody gets a stack trace.

There are no stdlib filter/map/reduce yet, and generics are new enough that most people are still writing the same for-range loops over and over. Lambdas don’t capture loop variable values.

x, y := f() sometimes assigns and sometimes shadows an outer scope.

defer isn’t block scoped, you have to simulate the code to figure out which calls are stacked at this point. Hopefully they’re added deterministically, but you can keep deferring stuff in a loop if you want.

(This is aside from the many ways Scala and Kotlin are far more readable than Java.)

Re:Go 1.19 Beta 1 is released by ainar-g on Saturday June 11, 2022 @03:42AM (#31702725)
Most of these are a part of the syntax though. When the parent comment talked about syntax, I'd assume that they said it the way most people say that Perl or Rust syntaxes are hard to read.

I agree about defer and the walrus operator though. Both can be quite confusing at times, and I think that Go with block-scoped defer and no walrus would be a more consistent language.

Re:Go 1.19 Beta 1 is released by johnisgood on Saturday June 11, 2022 @03:25AM (#31702661)
I thought that "if err != nil" is much less common now because of the changes in error handling. I personally do like "if err != nil" better. I can easily ignore that when I want, and I can easily check if I am handling the error properly without any cognitive overhead.
Re:Go 1.19 Beta 1 is released by erik_seaberg on Saturday June 11, 2022 @03:38AM (#31702707)
Have a link? I don’t see any changes in https://tip.golang.org/doc/go1.19 that seem likely to help.

How do you easily ignore the majority of the screen? Is there an editor plugin that just doesn’t display those ifs?

Re:Go 1.19 Beta 1 is released by ainar-g on Saturday June 11, 2022 @03:47AM (#31702736)
The fact that you think that error handling should be ignored is probably what prevents you from seeing the point of the Go error handling. The point is that one should never only consider the happy path. That one should actually think about how things can fail, what to do about those failures, and how to report those failures with enough context to figure something out on the outside if no appropriate handing is available in the code. Stack traces only give you line numbers. Properly used explicit error handling gives you more context in which a failure occurred.

Here's one example that might make it clearer: https://commandcenter.blogspot.com/2017/12/error-handling-in....

Re:Go 1.19 Beta 1 is released by joshuamorton on Saturday June 11, 2022 @04:15AM (#31702839)
You can write custom exceptions too.

If the only thing you're doing is saying `if err != nil { return nil, err }` anyway, which is what empirically the majority of go's error handling code does, yes, you should have a better way of representing that, whether it's a "?", ASSIGN_OR_RETURN, or exceptions, which take a single character, a single line, or a no characters at all, as opposed to golang's 3 lines of visual noise!

Saying that "you can use custom error types to give finer grained error information" is great and all, but I learned that in my CS101 class, in Java, in like 2012. It's not fancy or better or good, except compared to C. Its a worse way of doing a thing that Java and Python (and...) have been doing for decades.

Re:Go 1.19 Beta 1 is released by ainar-g on Saturday June 11, 2022 @04:28AM (#31702892)
Once again, you're referring to the conditional as “visual noise” as opposed to the actual thing that reminds you that there is a bifurcation here. The point is not to do this:

  // Bad, most of the time.
  result, err := foo(x)
  if err != nil {
          return err
  }
But to do this:

  // Better, most of the time.
  result, err := foo(x)
  if err != nil {
          return fmt.Errorf("performing foo on x = %v: %s", x, err)
  }
This isn't noise. This is meaningful logic. That is what exception mechanisms seem to discourage, as they are invisible (unless you wrap every call to everything that throws into a try{}, but then it's not better than an if{} is it?), and this is what the ? operator in some languages discourages as well, because it adds no human- or machine-readable context.

There must be syntax that indicates what to do when an error occurs, and that syntax must support addition of information about the context in which the error has occurred. And why not have the most basic conditional take the role of that syntax?

Re:Go 1.19 Beta 1 is released by joshuamorton on Saturday June 11, 2022 @01:39PM (#31706341)
That tells you absolutely no information a stacktrace doesn't. It's actually worse than just passing the err! Like, foo knew you failed performing foo, that's why you have the error, because foo failed. You don't need to reiterate that foo failed while performing foo, because the machine and user already know foo failed. See how annoying that kind of repetition is.

I've seen people that do that and it sounds nice until you end up with

Failed foo on x: failed bar on x: failed doing baz on x: failed to do quux".

You've created a worse stacktrace! I now have to search for a string and hope I can guess where the %s (or v or q) was instead of just grabbing the line number.

Or I do none of that, pass errors around directly, and just use the stacktrace.

The issue with your claim is that we only care about errors in two places, where we create them (like where the file was unable to be read) and where we handle them (when they are either swallowed bc the behavior was expected or passed to the user).

You don't care about them in all the intervening code, and exceptions handle that better.

> And why not have the most basic conditional take the role of that syntax?

Because it bloats your code and you end up with in practice more lines spent on verbose, cookie cutter error returning than actual logic!

Like, you don't need additional human readable context except in very particular cases. Go proves this in practice as almost everyone just returns the unmodified error most of the time, and it works great. Except for the annoying syntax.

Re:Go 1.19 Beta 1 is released by thayne on Saturday June 11, 2022 @03:21PM (#31707384)
> And why not have the most basic conditional take the role of that syntax?

Because having approx. 3/4 of your code devoted to error handling and error propagation is both hard to write and hard to read.

IMO rust's approach is close to ideal, in the common case where you just propagate up, the syntax is succinct, but still explicit, and when you handle it, the logic is close to the callsite, and is just working with a normal value. Useful stack traces are still a bit of a problem, but there is work being done on that.

And that's not to mention how in go you always return both the error and regular values, even though you usually only use one.

Re:Go 1.19 Beta 1 is released by 8n4vidtmkvmk on Saturday June 11, 2022 @05:07AM (#31703065)
even if you wrap in try catch its worse because it moves the error to the bottom, messes with your scopes, and you can't tell which line actually threw
Re:Go 1.19 Beta 1 is released by kaba0 on Saturday June 11, 2022 @06:21AM (#31703401)
Or — you can wrap logical parts into a try-catch block, because it doesn’t really makes sense to throw 263 different errors for the same logical unit of work.

Also, bubbling up is the sane default, even if you are writing a fast script/trying out some code it won’t clutter anything and you will be notified to handle the problems once you want to write robust code. While in Go you will just put empty if errs and will forget about the whole thing, swallowing errors which are arguably the worst thing.

Re:Go 1.19 Beta 1 is released by hdjrudni on Sunday June 12, 2022 @06:57PM (#31719044)
Yes, wrapping individual statements is better. But then it's still overly verbose and has weird scoping issues. e.g. in JS you might write:

try { let res = somethingThatMightFail(); catch(err) { // log the error or something return null; }

// res is good now... but it's out of scope

Whereas in C++ you'd just write

ASSIGN_OR_RETURN(auto res, somethingThatMightFail())

And it will bubble your error status just like you wanted, only takes 1 line of code, and keeps all the error information (assuming you're using absl::Status).

I haven't really used Go, but it sounds like the worst of both worlds.

> even if you are writing a fast script/trying out some code it won’t clutter anything and you will be notified to handle the problems once you want to write robust code

How are you going to go back and find every callsite that might potentially fail at a later date? There's no easy way to even tell if somethingThatMightFail might fail if it doesn't return something like a "StatusOr" or "Option" or something. I think Java has some tooling to force exception handling. Not sure about Go.

Re:Go 1.19 Beta 1 is released by kaba0 on Monday June 13, 2022 @03:43AM (#31722439)
Well, Java has checked exceptions which have to be handled at call site, or be declared as being thrown in the method handler (making it ‘viral’). I believe these solve this “find every callsite later” thing quite well.

While Java’s exceptions are not without problems (too deep inheritance trees don’t make sense on exception types, lambdas not operate too well with this feature, etc), I think it is a really good direction not utilized to the full by any mainstream language.

Re:Go 1.19 Beta 1 is released by ainar-g on Saturday June 11, 2022 @03:43AM (#31702728)
I'm not sure what you're talking about. Besides the standardization of error wrapping, there weren't any changes to how error handling is done.