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


Steven Schveighoffer <schvei...@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |schvei...@yahoo.com




--- Comment #4 from Steven Schveighoffer <schvei...@yahoo.com>  2009-07-17 
12:55:21 PDT ---
(In reply to comment #3)
> That's one reason.  The other reason is that it can do many things that a ref
> return can't, such as
> - converting the value to an internal representation
> - validating the set value
> - calling some external API to set the value
> - triggering side effects beyond setting the value in memory

All of these things are doable from a returned struct which contains opAssign.

I agree with the reporter that opIndexAssign is a feature that we could do
without, although you are correct in that removing opIndexAssign doesn't solve
his problem.

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

Reply via email to