undefined | Better HN

0 pointsXorNot4d ago0 comments

The problem with let's get rid of NULL is that it's a real, required state. The vast majority of computing is actually not binary: any real input generally has at least 3 possible states: not set, true and false.

In practice really 4 because "indeterminate" is a reasonable error condition you'd like to know about.

And it keeps increasing anyway: e.g. not set has subcategories: not set due to lack of user input, not set because we're loading state from the backend etc.

NULL is the first expression of that basic problem: it's definitely not enough to eliminate NULL because the first thing which happens is your non pointer default value takes it's place.

0 comments

2 comments · 1 top-level

lambdaone4d ago· 1 in thread

What you are describing is option types, which are an entirely valid and very useful construct that helps make programs more rather than less reliable. But you need proper language type system support and compile-time enforcement to make it work, and C does neither of those.

bnolsen4d ago

C++ and rust make these optionals ugly. Zig does it right. Zig also forbids null pointers and requires use of optionals.

j / k navigate · click thread line to collapse