Real Close to the Machine: Floating Point in D

The intention is to default-initialize values to things that are invalid. There's no obvious "invalid" value for a plain integer, so they get zero. But char gets 0xFF, because a char is defined to hold UTF-8 code units, and 0xFF is not a valid UTF-8 code unit. Similar logic extends to the larger character types, and to using NaN in a float.

The idea is that you should be initializing values explicitly before using them, and default-initializing to values which will rapidly fail makes it easier to debug use-before-initialization bugs than (for example) it is in C, where values are not initialized at all.

If you explicitly want to disable default initialization, you can use void as an initializer, as in:

int x = void;

I've found NaN initialization for floats to be a useful default (like undefined in Javascript) since it propagates.

Integer have no NaNs, so they are initialized with 0s since no other value really fits.

I don't know for chars but I guess there are good reasons as well.

On efficiency

The compiler cannot rely on the stack (or registers) to be zero, so there has to be a instruction to set it to zero anyways.

However, setting a register to zero is a special case and your hardware might be optimized for it.

https://randomascii.wordpress.com/2012/12/29/the-surprising-...

Maybe setting to zero would faster. However, if you optimize on that level, then you can optimize by hand as well. Set it to zero explicitly or even let it uninitialized explicitly:

    int x = void;