On Saturday, 27 February 2021 at 13:32:24 UTC, Paul Backus wrote: > The compiler will still allow you to > void-initialize/overlap/reinterpret-cast an Unsafe!size_t in > @safe code, because it considers size_t to be a safe type. The wrapped value still won't be accessible to safe code.