undefined | Better HN

0 pointsgoodoldneon2y ago0 comments

Go can be `tuple[User | None, Exception | None]` or `tuple[User, Exception | None]`, depending on whether you're returning a pointer. But yea, Go's approach has its warts. Like if you aren't returning a pointer then you need to return the zero value (e.g. `User{}`) even when returning an error

0 comments

progbits2y ago

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.

goodoldneonOP2y 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 pointsgoodoldneon2y ago0 comments

0 comments

progbits2y ago

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.

goodoldneonOP2y 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