Re:Error stack traces in Go with x/xerror
by OJFord on Monday August 23, 2021 @09:22PM
(#28284102)
That's true, it's a while since I did only a little bit of Haskell, but yes. I suppose I didn't think of it because it feels less like 'having to handle' it in Haskell, since that's the norm anyway.
Whereas if you compare Rust to Python, C(++), or Go as I was - having to consume a returned 'result' is more notable.
Whereas if you compare Rust to Python, C(++), or Go as I was - having to consume a returned 'result' is more notable.