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





--- Comment #11 from Stewart Gordon <s...@iname.com>  2009-07-27 09:22:16 PDT 
---
(In reply to comment #4)
> (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.

But it would make code unnecessarily complex, and make the compiler have to
work harder to optimise it to something as well-performing as a simple
opIndexAssign.

(In reply to comment #10)
> You are confusing opMul with opStar.

Yet another reason opStar was the wrong choice of name, besides inconsistency.

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

Reply via email to