https://svn.boost.org/trac10/ticket/4279 <p> There is a need for two version of this class. </p> <p> First version is the same as current with addition of patch from tick <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/3869" title="#3869: Bugs: Unconditional call to memset in value_initialized() (closed: fixed)">#3869</a>. Second version doesn't call to memset in any case. </p> <p> The second version might not work with all cases but sometimes it is needed to guarantee that memset will not be called. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/4279 Trac 1.4.3 Steven Watanabe Wed, 02 Jun 2010 16:05:48 GMT https://svn.boost.org/trac10/ticket/4279#comment:1 https://svn.boost.org/trac10/ticket/4279#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> <p> Why do you need to /guarantee/ that memset won't be called? The only reason for calling memset is to work around compiler bugs. I see no reason for a class to silently do the wrong thing instead of taking a minor performance penalty. </p> Ticket