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

Add missing closing brace.

Browse Source
This commit is contained in:
Andreas Scherer
2015-10-18 10:48:40 +02:00
parent 8221bd9016
commit 41f1c30d1c
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

@@ -3393,7 +3393,7 @@ These operations disagree about copy semantics. This will lead to confusion and
"Does this class need a destructor?" is a surprisingly powerful design question. "Does this class need a destructor?" is a surprisingly powerful design question.
For most classes the answer is "no" either because the class holds no resources or because destruction is handled by [the rule of zero](#Rc-zero); For most classes the answer is "no" either because the class holds no resources or because destruction is handled by [the rule of zero](#Rc-zero);
that is, its members can take care of themselves as concerns destruction. that is, its members can take care of themselves as concerns destruction.
If the answer is "yes", much of the design of the class follows (see [the rule of five](#Rc-five). If the answer is "yes", much of the design of the class follows (see [the rule of five](#Rc-five)).
### <a name="Rc-dtor"></a> C.30: Define a destructor if a class needs an explicit action at object destruction ### <a name="Rc-dtor"></a> C.30: Define a destructor if a class needs an explicit action at object destruction