From 7e4a683c965830583a2aed635f4bb854fa4e3192 Mon Sep 17 00:00:00 2001 From: rkawulak Date: Mon, 21 Sep 2015 23:35:19 +0200 Subject: [PATCH] Lots of minor fixes (typos, code errors, formatting, etc.) --- CppCoreGuidelines.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 9b54245..b9a08c6 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -1150,7 +1150,7 @@ Better still, use [RAII](#Rr-raii) to ensure that the postcondition ("the lock m void manipulate(Record& r) // best { - lock_guard _ {m}; + lock_guard _ {m}; // ... } @@ -2723,7 +2723,7 @@ 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.11: Make a concrete types regular](#Rc-regular) +* [C.11: Make concrete types regular](#Rc-regular) ### C.10 Prefer a concrete type over more complicated classes @@ -2770,7 +2770,7 @@ This is done where dynamic allocation is prohibited (e.g. hard real-time) and to **Enforcement**: ??? -### C.11: Make a concrete types regular +### C.11: Make concrete types regular **Reason**: Regular types are easier to understand and reason about than types that are not regular (irregularities requires extra effort to understand and use). @@ -8324,7 +8324,7 @@ Let cleanup actions on the unwinding path be handled by [RAII](#Re-raii). void f(int n) { void* p = malloc(1, n); - auto __ = finally([] { free(p); }); + auto _ = finally([] { free(p); }); // ... }