Re:Sub-millisecond GC pauses in Go 1.8
by premium-concern on Saturday October 29, 2016 @09:48AM
(#12823906)
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)?
You only have to check 1 case in Go (`if err != nil { ... }`). What language lets you check half a case?
Re:Sub-millisecond GC pauses in Go 1.8
by premium-concern on Saturday October 29, 2016 @12:29PM
(#12824696)
(int64, error)
gives you exactly four possibilities.Either gives you exactly the two you want.
Please feel free to enumerate them.
Re:Sub-millisecond GC pauses in Go 1.8
by premium-concern on Saturday October 29, 2016 @02:00PM
(#12825311)
(value, no error)
(value, error)
(no value, error)
(no value, no error)
Re:Sub-millisecond GC pauses in Go 1.8
by leaveyou on Saturday October 29, 2016 @03:22PM
(#12825809)
The convention is that if the err == nil then the value is not nil. The exceptions to this rule are very few and usually specified in the documentation. Normally you only have to check for error.
Re:Sub-millisecond GC pauses in Go 1.8
by bluejekyll on Saturday October 29, 2016 @06:07PM
(#12826687)
The fact that it's a convention, and not a compiler error is the entire issue at debate here.
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 ?