http://d.puremagic.com/issues/show_bug.cgi?id=6906
Don <clugd...@yahoo.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code --- Comment #3 from Don <clugd...@yahoo.com.au> 2011-11-08 22:59:29 PST --- (In reply to comment #2) > Can I then say you aren't able to define opAssign for a struct and have it > work > for associative arrays: > > /tmp$ ./test > Segmentation fault That's definitely a problem, but I don't think it has anything to do with AAs. This also creates a stack overflow: void main() { S s; S t; t = s; } struct S { void opAssign(S s) { this = s; } } Obviously it's changing 'this = XXX' into 'this.opAssign(XXX)'. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------