noexcept

Imagine I'm writing some container template or something. And the time comes to specialize std::swap for it. As a good citizen, I'll enable ADL by doing something like this: template <typename T> void swap(my_template<T>& x, my_template<T>& y) { using std::swap; swap(x.something_that_is_a_T, y.something_that_is_a_T); } This is very neat and all. Until I want to add an exception specification. My swap is noexcept as long as the swap for T is noexcept . So, I'd be writing something like: template <typename T> void swap(my_template<T>& x, my_template<T>& y) noexcept(noexcept(swap(std::declval<T>(

Is there any other difference between throw() and noexcept apart from being checked runtime and compile time respectively ? Wikipedia C++11 article suggests that C++03 throw specifiers are deprecated. Why so, is noexcept capable enough to cover all that at compile time ? [Note: I referred this question and this article , but couldn't got the solid reason of deprecation.] Nicol Bolas Exception specifiers were deprecated because exception specifiers are generally a terrible idea . noexcept was added because it's the one reasonably useful use of an exception specifier: knowing when a function won

The noexcept keyword can be appropriately applied to many function signatures, but I am unsure as to when I should consider using it in practice. Based on what I have read so far, the last-minute addition of noexcept seems to address some important issues that arise when move constructors throw. However, I am still unable to provide satisfactory answers to some practical questions that led me to read more about noexcept in the first place. There are many examples of functions that I know will never throw, but for which the compiler cannot determine so on its own. Should I append noexcept to