x.RC.__postblit () is not callable using argument types () const
Maxim Fomin
maxim at maxim-fomin.ru
Tue Feb 5 03:50:33 PST 2013
On Tuesday, 5 February 2013 at 01:15:28 UTC, Dan wrote:
> I've seen these type of errors often and usually the cause kind
> of jumps out. In this case I'm totally confused. Just trying to
> move from 2.06 to 2.061.
>
> The code is: http://dpaste.dzfl.pl/f40e4d6f
> and fails with the error in subject line. Observations:
>
> - If "static if(1)" is changed to "static if(0)" it compiles
> - If either _valuationHistory or goo member of BSItem is
> commented out it compiles.
>
> I know the code is somewhat cryptic, but I've been using binary
> reduction comment in/out to try to narrow down this issue. I
> can not understand why an introduction of opEquals on a struct
> History with no relationship to RC causes an error to show for
> RC.
>
> Thanks
> Dan
There is still problem with const structs vs. non-const postblit
and destructor. In the past, the situation was even worse, but
was partly fixed by laxing constness with respect to postblit and
destructor. Now all such problems seems to come from associative
array implementation in object.d
More information about the Digitalmars-d-learn
mailing list