OpIndex/OpIndexAssign strange order of execution

[Moritz Maxeiner]

On Monday, 18 September 2017 at 15:11:34 UTC, Moritz Maxeiner 
wrote:
>
> gets rewritten to
>
> ---
> t.opIndex("b").opIndexAssign(t["a"].value, "c");
> ---

Sorry, forgot one level of rewriting:

---
t.opIndex("b").opIndexAssign(t.opIndex("a").value, "c");
---