Mirrors/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2025-12-18 13:14:40 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix discussion link in C.36 (#1523)

Browse Source
This commit is contained in:
shaneasd
2019-10-11 02:30:51 +08:00
committed by Herb Sutter
parent 3f70be9721
commit 56a941a7f8
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CppCoreGuidelines.md
View File

@@ -4998,7 +4998,7 @@ Many have tried to devise a fool-proof scheme for dealing with failure in destru
None have succeeded to come up with a general scheme. None have succeeded to come up with a general scheme.
This can be a real practical problem: For example, what about a socket that won't close? This can be a real practical problem: For example, what about a socket that won't close?
The writer of a destructor does not know why the destructor is called and cannot "refuse to act" by throwing an exception. The writer of a destructor does not know why the destructor is called and cannot "refuse to act" by throwing an exception.
See [discussion](#Sd-dtor). See [discussion](#Sd-never-fail).
To make the problem worse, many "close/release" operations are not retryable. To make the problem worse, many "close/release" operations are not retryable.
If at all possible, consider failure to close/cleanup a fundamental design error and terminate. If at all possible, consider failure to close/cleanup a fundamental design error and terminate.