StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

resolve #1209, #814, and #167

Browse Source 
noexcept and destructors
This commit is contained in:
Bjarne Stroustrup 2018-09-03 13:50:10 -04:00
parent f3e7dbac6e
commit d3c3e3aa98
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
CppCoreGuidelines.md
View File

@ -5000,6 +5000,23 @@ If a destructor uses operations that may fail, it can catch exceptions and in so
A destructor (either user-defined or compiler-generated) is implicitly declared `noexcept` (independently of what code is in its body) if all of the members of its class have `noexcept` destructors. By explicitly marking destructors `noexcept`, an author guards against the destructor becoming implicitly `noexcept(false)` through the addition or modification of a class member.
##### Example
Not all destructors are noexcept by default; one throwing member poisons the whole class hierarchy
struct X {
Details x; // happens to have a throwing destructor
// ...
~X() { } // implicitly noexcept(false); aka can throw
};
So, if in doubt, declare a destructor noexcept.
##### Note
Why not then declare all destrouctors noexcept?
Because that would in many cases -- especially simple cases -- be distracting clutter.
##### Enforcement
(Simple) A destructor should be declared `noexcept` if it could throw.