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

clarifications for #1267

Browse Source 
references to resource handles
This commit is contained in:
Bjarne Stroustrup
2018-10-12 15:27:55 -04:00
parent 11f58787b8
commit 417d512fea
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CppCoreGuidelines.md
View File

@@ -4392,6 +4392,7 @@ The allocation/deallocation overhead is not (that's just the most common case).
We can use a base class as the interface of a scoped object of a derived class. We can use a base class as the interface of a scoped object of a derived class.
This is done where dynamic allocation is prohibited (e.g. hard-real-time) and to provide a stable interface to some kinds of plug-ins. This is done where dynamic allocation is prohibited (e.g. hard-real-time) and to provide a stable interface to some kinds of plug-ins.
##### Enforcement ##### Enforcement
??? ???
@@ -4422,6 +4423,13 @@ Regular types are easier to understand and reason about than types that are not
In particular, if a concrete type has an assignment also give it an equals operator so that `a = b` implies `a == b`. In particular, if a concrete type has an assignment also give it an equals operator so that `a = b` implies `a == b`.
##### Note
Handles for resources that cannot be cloned, e.g., a `scoped_lock` for a `mutex`, resemble concrete types in that they are most often be stack_allocated.
However, objects of suct types typically cannot be copied (instead, they can usually be moved),
so they can't be `regular`; instead, they tend to be `semiregular`.
Often, such types are referred to as "move-only types".
##### Enforcement ##### Enforcement
??? ???