Live data from Hacker News

The Golden Rule of Programming

stackify.com

11–20 of 20 posts

Re: The Golden Rule of Programming

#16

"If it can be null, it will be null" So explicitly define what is allowed to ever be "null": http://lukeplant.me.uk/blog/posts/null-pointers-vs-none-vs-m...

Would that we could all just up and switch programming languages at the drop of a hat like that.

Explicitly defining what is ever allowed to be 'null' is a great habit that serves me extremely well during evenings and weekends. But it's completely useless to me, by virtue of being impossible, between 9am and 5pm.

Re: The Golden Rule of Programming

#17

I'm not a C# coder but I understood it was possible to have non-nullable types? Keep meaning to try C# for a project sometime. I understand it to be a more expressive, programmer friendly Java.

Value types are non-nullable. But they're also stack-allocated* and passed by value, so they're really only appropriate in certain cases. You can't use them as general-purpose non-nullable objects.

*In practice, though technically that bit's an implementation detail of Microsoft's run-time and not part of the language spec.

Post reply on HN