4 ms·
it's the other way around Rust used to not have operator?, and then A LOT of complaints have been "we don't care, just let us pass errors up quickly" "good lu
by NooneAtAll3 11mo ago
it's the other way around
Rust used to not have operator?, and then A LOT of complaints have been "we don't care, just let us pass errors up quickly"
"good luck debugging" just as easily happens simply by "if err!=nil return nil,err" boilerplate that's everywhere in Golang - but now it's annoying and takes up viewspace
- oncallthrow 11mo ago> "if err!=nil return nil,err" boilerplate that's everywhere in Golang - but now it's annoying and takes up viewspace This isn't true in my experience. Most Go codebases I've worked in wrap their errors. If you don't believe me, go and take a look at some open-source Go projects.