1 Jun
2017
1 Jun
'17
6:52 a.m.
On Wed, May 31, 2017 at 4:34 PM, Niall Douglas via Boost
Well, apart from poor quality of implementation of std::variant sometimes. For example, libstdc++'s for GCC 7.1 appears to always use type erased memory allocation. Which, frankly, is daft in C++ 14 when you are storing either an int or a std::error_code. I would also assume that std::bad_alloc can be thrown from libstdc++'s std::variant<> :(
{{citation needed}}. libstdc++'s <variant> may have problems, but dynamic allocation (which would be completely nonconforming) is not one of them.