On Wednesday, 9 January 2013 at 18:17:52 UTC, monarch_dodra wrote:
The "good news" is that since the values are T.init'd, then opEqual becomes somewhat more valid, although arguably, it should really be in-place construction, *especially* if immutable is involved (or types without opAssign...).
Wait, never mind. That's only a special case in Appender's implementation. Since it mallocs the rest of the time, this doesn't hold, and anything with a constructor (or just) will not be correctly initialized :/
