core-guidelines
- A fork with my simplified reading notes.
Why guidelines
as with all general principles, its value lies not in being an absolute rule for every case, but rather a default rule, a guideline that should be followed in the absence of a good reason not to; the reality is that the majority of everyday work is not special and the result is better if this principle is followed. -- from: Hands-On Design Patterns with C++
Completed
- C: Classes and class hierarchies
- C.concrete: Concrete types
- C.defop: Default Operations
- C.dtor: Destructors
- C.ctor: Constructors, assignments, and destructors
- C.copy: Copy and move
- C.other: Other default operation rules
- C.con: Containers and other resource handles
- C.lambdas: Function objects and lambdas
- C.hier: Class hierarchies (OOP)
- C.hierclss: Designing classes in a hierarchy
- C.hier-access: Accessing objects in a hierarchy
- C.over: Overloading and overloaded operators
- C.union: Unions
- Enum: Enumerations
- R: Resource management
- ES: Expressions and statements
- Per: Performance
- CP: Concurrency and parallelism
- E: Error handling
- Con: Constants and immutability
- T: Templates and generic programming
- F: Functions
- I: Interfaces
- SL: The Standard Library
- NL: Naming and layout rules
- P: Philosophy
- Pro: Profiles
- SF: Source files
- A: Architectural ideas
- NR: Non-Rules and myths
- CPL: C-style programming
- GSL: Guidelines support library
- Appendix C: Discussion