Bug 8915 – Current lvalue behavior looks inconsistent for structs and buildin types

--- int iFunc() { return 0; }; enum int iEnum = iFunc(); struct S { } S sFunc() { return S(); }; enum S sEnum = sFunc(); void refI(ref int) { } void refS(ref S) { } void main() { refI(int.init); // Error: constant 0 is not an lvalue refI(iEnum); // Error: constant 0 is not an lvalue refI(iFunc()); // Error: iFunc() is not an lvalue refS(S()); // compiles refS(S.init); // compiles refS(sFunc()); // Error: f() is not an lvalue refS(sEnum); // compiles } --- This leads to inability to define `NonZeroUInt32` struct e.g. with same semantics as `uint`.

Now all give errors.

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