Four levels of in-place initialization

An in-depth proposal argues that Rust's in-place initialization problem should be solved not with a single feature but with a four-level hierarchy: raw pointers with MaybeUninit (most flexible, unsafe), a proposed &uninit/&own reference pair for safe first-class uninitialized places, 'placing functions' that rewrite return to write into an out-pointer without changing function signatures, and automatic MIR-level move elimination (an optimization, not guaranteed semantics) as proposed in RFC 3943. The piece walks through code examples for each level, compares their expressivity, safety, signature impact, and semantic guarantees, and concludes that Rust should offer complementary high-level and low-level primitives rather than one universal mechanism, similar to how const works today.

Source: https://blog.yoshuawuyts.com/four-levels-of-in-place-initialization. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.