https://issues.dlang.org/show_bug.cgi?id=15627
Walter Bright <bugzi...@digitalmars.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |bugzi...@digitalmars.com Resolution|--- |WONTFIX --- Comment #1 from Walter Bright <bugzi...@digitalmars.com> --- What's happening is the .init is insufficient to initialize foo, because local structs are also initialized with a runtime dynamic link to the stack frame of the caller. The .init has this field set to null. Technically, this is not an @safe issue because @safe does not care about null pointer accesses, because null pointer accesses are not memory safety issues. Semantically, this case is no different from: @safe void foo() { int* p = null; *p = 3; } which will also compile successfully and seg fault at runtime. If this issue were 'fixed', how would one explain that the pointer init to null issue is legal but the local struct init to null is not? I suspect that the cure would be worse than the problem, so I am going to mark this as wontfix. ---------------------------- The program will run successfully if you let the compiler do the initialization, as in replace: FooType foo = FooType.init; with: FooType foo; --