[Issue 6216] Built-in opAssign implicitly defined should call field's opAssign

d-bugmail at puremagic.com d-bugmail at puremagic.com
Sun Oct 7 09:27:14 PDT 2012


http://d.puremagic.com/issues/show_bug.cgi?id=6216



--- Comment #1 from github-bugzilla at puremagic.com 2012-10-07 09:15:13 PDT ---
Commit pushed to master at https://github.com/D-Programming-Language/dmd

https://github.com/D-Programming-Language/dmd/commit/b9896d14766fe5a067cf84d0d2c21418dfb35676
fix Issue 6216 - Built-in opAssign implicitly defined should call field's
opAssign

Separate 'top assignable' (see opAssign first) from 'blit assignable'
(memberwise), and now they are not related to 'modifiable' directly.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list