I&#39;ve just begun having issues with some use of boost::optional producing the error shown in the subject.<br><br>This is a gcc bug, filed at <a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47679">http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47679</a><br>

The corresponding downstream bug for RedHat/Fedora is at <a href="https://bugzilla.redhat.com/show_bug.cgi?id=676361">https://bugzilla.redhat.com/show_bug.cgi?id=676361</a> and has a code listing to reproduce.<br><br>Sending this partially as an FYI, and also to ask if anyone has any workaround?<br>

Altering client code to construct with boost::none or a false condition, then assigning a value if required, still yields the error on the assign operation.<br><br>My current workaround is to initialize the optional&lt;T&gt; in question with a dummy T instance, then call reset() with no params if I want an &#39;uninitialized&#39; optional.<br>

It looks rather bizarre, but if it must be then it must be.<br><br><br clear="all"><br>-- <br>Rob Desbois<br>Eml: <a href="mailto:rob.desbois@gmail.com" target="_blank">rob.desbois@gmail.com</a><br>Blog: <a href="http://theotherbranch.wordpress.com/" target="_blank">http://theotherbranch.wordpress.com/</a><br>