mirror of
https://github.com/isocpp/CppCoreGuidelines.git
synced 2024-03-22 13:30:58 +08:00
Clarifying title per issue 793
This commit is contained in:
parent
8a9bb3bc61
commit
9858685786
@ -3774,17 +3774,17 @@ Concrete types are also often referred to as value types to distinguish them fro
|
||||
|
||||
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)
|
||||
|
||||
### <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
|
||||
|
||||
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.
|
||||
You need a reason (use cases) for using a hierarchy.
|
||||
|
||||
n
|
||||
##### Example
|
||||
|
||||
class Point1 {
|
||||
|
Loading…
x
Reference in New Issue
Block a user