the flag is always `false` already when calling `setInitializer()`.

As for not automatically setting it to `false`, I think that denies usage of a more complex initializer.

I may change this behavior and enforce setting the initializer again explicitly instead of having users set it to `null` manually, but only for `1.x` or even `2.x`