--- Comment #5 from Andrei Alexandrescu <> 2010-06-02 
08:57:50 PDT ---
That looks like a very specialized optimization to me. In particular, if the
postblit has side effects, the optimizer must have advanced knowledge in order
to elide it. This is a path that C++ has taken with copy constructor elision,
and it's not a path we should take.

I think the language definition should clarify that postincrement and
postdecrement are lowered into their pre- counterparts if the result is not

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to