[Issue 9732] Do not call opAssign() for the first assignment to member in the constructor

[d-bugmail at puremagic.com]

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



--- Comment #4 from monarchdodra at gmail.com 2013-03-17 07:21:15 PDT ---
(In reply to comment #1)
> The problem is that opAssign can perform deep copy operations for which
> blitting isn't enough.

That's why we have postblit. If anything, I'd expect postblit to be safer then
opAssign: postblit has no pre-state, whereas opAssign may make assumptions
about it's current (run-time initialized?) state.

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