sob., 2 mar 2019 o 06:04 Emil Dotchevski via Boost
On Fri, Mar 1, 2019 at 8:55 PM Andrzej Krzemienski via Boost < boost@lists.boost.org> wrote:
2. this state is actually read instead of being destroyed (or overwritten)
Why does it have to be read instead of destroyed?
Because it is only when you try to read the state of such object, being observably valueless or not makes any difference. The reason why
valid-but-unspecified is useful is not because reading it is somehow desirable, but because it could happen. It's better than seeing pink elephants.
My hypothesis is that reading valid-but-unspecified can only happen in a buggy program in an unintended path. And that making design compromises to address this path is not necessarily the best approach to take. Regards, Andrzej
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost