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

Clarifying title per issue 793

Browse Source
This commit is contained in:
Andrew Pardoe
2017-01-30 11:36:57 -08:00
parent 8a9bb3bc61
commit 9858685786
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CppCoreGuidelines.md
View File

@@ -3774,17 +3774,17 @@ Concrete types are also often referred to as value types to distinguish them fro
Concrete type rule summary: Concrete type rule summary:
* [C.10: Prefer a concrete type over more complicated classes](#Rc-concrete) * [C.10: Prefer a concrete types over class hierarchies](#Rc-concrete)
* [C.11: Make concrete types regular](#Rc-regular) * [C.11: Make concrete types regular](#Rc-regular)
### <a name="Rc-concrete"></a>C.10 Prefer a concrete type over more complicated classes ### <a name="Rc-concrete"></a>C.10 Prefer a concrete types over class hierarchies
##### Reason ##### Reason
A concrete type is fundamentally simpler than a hierarchy: A concrete type is fundamentally simpler than a hierarchy:
easier to design, easier to implement, easier to use, easier to reason about, smaller, and faster. easier to design, easier to implement, easier to use, easier to reason about, smaller, and faster.
You need a reason (use cases) for using a hierarchy. You need a reason (use cases) for using a hierarchy.
n
##### Example ##### Example
class Point1 { class Point1 {