undefined | Better HN

0 pointsprogbits2y ago0 comments

Yeah but pointer + nil also have issues: https://go.dev/doc/faq#nil_error

I've also seen APIs that allow returning both error and a value ("something went wrong, but here is a fallback or something") which are of course extremely confusing given the usual style.

0 comments

goodoldneon2y ago

Oh I agree, I've run into too many nil pointer panics. I wish Go had a first-class way of expressing optionality, rather than using pointers

j / k navigate · click thread line to collapse

0 comments

goodoldneon2y ago

Oh I agree, I've run into too many nil pointer panics. I wish Go had a first-class way of expressing optionality, rather than using pointers

j / k navigate · click thread line to collapse