Bug 655 – Operator overload uses opIndex instead of opIndexAssign

In an array assignment expression, operator overload uses opIndex instead of opIndexAssign. ---------- import std.stdio; struct Moo { void opIndex(int i, int i2) { writefln("opIndex:", i, i2); } } int main(char[][] args) { Moo m = *new Moo(); m[0, 42]; // uses opIndex , ok m[0] = 42; // uses opIndex instead of opAssign, not ok according to spec return 0; }

Agh, read the comment above as: m[0] = 42; // uses opIndex instead of opIndexAssign, not ok according to spec

> import std.stdio; > > struct Moo { > void opIndex(int i, int i2) { > writefln("opIndex:", i, i2); > } > } > > int main(char[][] args) { > Moo m = *new Moo(); > m[0, 42]; // uses opIndex , ok > m[0] = 42; // uses opIndex instead of opAssign, not ok according to spec > > return 0; > } > When I compile that snippet in 0.176, I get the error: dtest.d(134): Error: operator [] assignment overload with opIndex(i, value) deprecated, use opIndexAssign(value, i) Is that what you mean? Or does it compile for you? I think it's a vestige of some _very_ old operator overloading behavior, Walter probably missed it.

My mistake, I was compiling with -d (allow deprecated) and didn't notice it.