I have a hurdle with noexcept specifier next to my copy constructor.I'm not sure if I should put noexcept next to copy constructor while there is std::make_unique that can throw bad_alloc.
Is there any reason that std::deque's pop_front() and pop_back() are not noexcept in C++11 and higher or was that just forgotten?
Is this possible? I don't think it is, but I don't know if this is something the standard would say, or if it's implementation defined? I'm asking because I'm wondering whether it's safe or worth it to mark a constexpr function like this noexcept
If I construct an empty std::vector using the default constructor (and the default allocator), can it throw an exception?
Take the following example code:Assume that, once item has been passed to the function, this cannot throw.
The code in question isIt compiles on gcc 8, but fails on clang 6 with the following error:Remove the noexcept specifier on func()