4 ms·
> That's a consequence of the "always mutable" model whereby the responsibility of initialization can be shared by the object constructor and the caller. It's
by masklinn 6y ago
> That's a consequence of the "always mutable" model whereby the responsibility of initialization can be shared by the object constructor and the caller.
It's not though. An "always mutable" model can require that objects be fully initialised up-front. Rust does exactly that.