On 8/4/22 9:51 PM, Paul Backus wrote:
On Friday, 5 August 2022 at 01:47:07 UTC, Ruby The Roobster wrote:
I found the issue: opOpAssign isn't getting called at all. I have no
idea why, though.
Given that the example works, the problem must be in some other part of
your code that you haven't posted. If you can post a more complete
example that reproduces the problem, we can probably help you fix it.
Another option: use -vcg-ast, and have the compiler tell you what it's
actually calling. It's not ignoring that line, it's just not doing what
you think it's doing.
-Steve
