News for hackers. Stuff that matters.

A comment on Go nulls and SQL. Parent comment

Re:Go nulls and SQL by tedunangst on Monday May 23, 2022 @04:28PM (#31484426)
There are some differences here, but you can't for instance use a string pointer with string functions in go either. IMO The distinction between pointer and optional is not as vast as people make it out to be.

(But thanks, I overlooked T? conversions inside if.)

[ Parent | on HN ]
Re:Go nulls and SQL by ricardobeat on Monday May 23, 2022 @08:23PM (#31486544)
No you can't, but Go will happily de-reference the pointer without a null check, and your "string" will blow up in production: https://go.dev/play/p/7EVa7q6VgIM
[ Parent | on HN ]
Re:Go nulls and SQL by akavi on Monday May 23, 2022 @05:37PM (#31485070)
The distinction between pointer and optional is not vast. The distinction between pointer and not optional is.

The whole idea of optional is to make not optional possible.

[ Parent | on HN ]
Re:Go nulls and SQL by morelisp on Monday May 23, 2022 @04:55PM (#31484666)
You can call a value method on a nil pointer and it panics, though, which I think was a mistake.
[ Parent | on HN ]
Re:Go nulls and SQL by nemothekid on Tuesday May 24, 2022 @02:09AM (#31488575)
>The distinction between pointer and optional is not as vast as people make it out to be.

The billion dollar mistake is overblown?

[ Parent | on HN ]