Pedr Ferreira Wrote:

> Walter Bright Wrote:
> 
> > Extrawurst wrote:
> > > "
> > > opAssign can no longer be overloaded for class objects.
> > > "
> > > 
> > > why is that ? that change breaks lots of my code... ;(
> > 
> > I didn't realize anyone was using it. What are you using it for?
> 
> I was using it for my Matrix class to index specific positions on the matrix. This will make me have to refactor A LOT of my code. I won't be upgrading to DMD 2.10 (sticking with 2.9) until this change becomes permanent.

Oh, nvm, opAssign isn't that bad, only minor modifications are necessary. I misread ad "ofIndexAssign", sorry about that.

Anyway, the page http://www.digitalmars.com/d/operatoroverloading.html still has the opAssign.

Pedr Ferreira wrote:
> Pedr Ferreira Wrote:
> 
>> Walter Bright Wrote:
>>
>>> Extrawurst wrote:
>>>> "
>>>> opAssign can no longer be overloaded for class objects.
>>>> "
>>>>
>>>> why is that ? that change breaks lots of my code... ;(
>>> I didn't realize anyone was using it. What are you using it for?
>> I was using it for my Matrix class to index specific positions on the matrix. This will make me have to refactor A LOT of my code. I won't be upgrading to DMD 2.10 (sticking with 2.9) until this change becomes permanent.
> 
> Oh, nvm, opAssign isn't that bad, only minor modifications are necessary. I misread ad "ofIndexAssign", sorry about that.
> 
> Anyway, the page http://www.digitalmars.com/d/operatoroverloading.html still has the opAssign.

I think it's staying for structs.  But the page should mention that.

--bb