[PeCaN]

The compiler provides you no help at all with them, and no syntax that makes error conditions and handling separate. It also mixes application logic and recovery logic.

Basically everything that's problematic with returning a status int in C, but all new, hip, and backed up by Rob Pike's pseudointellectual bullshit and a bunch of Silicon Valley 20somethings.

They could at least, you know, have an Either type or something. Anything?

[leaveyou]

>It also mixes application logic and recovery logic.

When did this separation become law ? What if the "application logic" requires recovery ?

>They could at least, you know, have an Either type or something

(int64, error) in func ParseInt() (int64, error) is your Either type. And checking if you got the "left or the right side of the Either" is IMHO much shorter and clearer than in Scala.

https://golang.org/pkg/strconv/#ParseInt

http://www.scala-lang.org/api/rc2/scala/Either.html

>backed up by Rob Pike's pseudointellectual bullshit and a bunch of Silicon Valley 20somethings

Why the ad hominems ?

[premium-concern]

cringe.

How ecactly is having to check twice the amount of cases an improvement (note btw, that checking for Left/Right is doing it wrong)?

[weberc2]

You only have to check 1 case in Go (`if err != nil { ... }`). What language lets you check half a case?

[premium-concern]

  (int64, error)

gives you exactly four possibilities.

Either gives you exactly the two you want.

[weberc2]

Please feel free to enumerate them.

[premium-concern]

  (value, no error)
  (value, error)
  (no value, error)
  (no value, no error)

[pjmlp]

Yes, but at least they are making the tools we may eventually have to rely on due to market pressure (Docker, K8s, ...) in Go instead of C.

[Artemis2]

Don't forget Brian Kernighan and Ken Thompson!