jmsdnns, 3 months ago

@winni not as badly as when #rust hackers have to write if err != nil a godzillion times

corpsmoderne, 3 months ago

@jmsdnns @winni is this a joke I'm not getting? because err != nil is a Go thing not a Rust thing...

dedsyn4ps3, 3 months ago

@corpsmoderne @jmsdnns @winni aaannd of course you can always abstract the error check into a function which you can call instead of typing that out each time 🙃 :golang:

func checkError(err error) {
if err != nil {
fmt.Println("An error occurred:", err)
}
}

jmsdnns, 3 months ago

@dedsyn4ps3 @corpsmoderne @winni my point is that go makes rust hackers go mad with such careless error handling

dedsyn4ps3, 3 months ago

@jmsdnns @corpsmoderne ahh gotcha. So your point of view is that the error handling used in Go is careless?

I'm curious what makes it so. I personally thought it to be nice having a language that stresses at least checking for returned errors more thoughtfully than in other languages.

Now of course, Rust tends to take things a step farther, but I wouldn't say that makes Go careless by any means...