Bug 14643 – Safety violation with final switch and void initializer

This compiles: ``` enum E { A, B } int* foo() @safe { E value = void; static int a, b; final switch (value) { case E.A: return &a; case E.B: return &b; } } void main() @safe { *foo() = 43; } ``` Throws core.exception.SwitchError in normal mode but crashes in release mode by trying to write via garbage pointer.

correction : foo() needs to be called twice to start getting garbage on stack

Note that an enum E is allowed to take values larger than E.max using binary operations: enum E { a, b} pragma(msg, E.max); // E.b which is 1 E value = E.b << E.b; // 2 So that violates `final switch` anyway, even in @safe code, and casting can (see https://issues.dlang.org/show_bug.cgi?id=11051#c7). Though void initialization is worse because the bug might not even be reproducible. Sadly void initialization is not banned in @safe.

> the bug might not even be reproducible Oops, the original bug also violates safety anyway. The above comment combined with the original example means that any enum value outside its min and max properties can produce an uninitialized pointer in safe code, void initialization is not required. The solution seems to be to fix issue 11051.

*** This issue has been marked as a duplicate of issue 11051 ***