http://d.puremagic.com/issues/show_bug.cgi?id=9218



--- Comment #10 from Kenji Hara <k.hara.pg@gmail.com> 2013-01-10 22:08:42 PST ---
(In reply to comment #9)
> Ok, that workabout is not quite complete (perhaps this is a different bug now?). While it solves the code in the original comment, this code doesn't work:
> 
[snip]
> 
> Why would enum A zero = A(); work but enum A zero = {}; not work? Is it safe
> (in terms of inadvertent GC usage) to use A() instead of {}?

This is a different bug which is unrelated to the ref-non-ref overloading. I opened a new bug report.

Issue 9293 - enum struct with StructInitializer reports weird error

So this is an invalid bug, because:

(In comment #1)
> Struct literals (manifests included) are no longer lvalues in 2.061, this is by
design.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

http://d.puremagic.com/issues/show_bug.cgi?id=9218


Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


--- Comment #11 from Walter Bright <bugzilla@digitalmars.com> 2013-01-28 15:28:53 PST ---
We still need to address the rvalue ref issue, but at the moment this is invalid because it's by design.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------