From 52852dc7d685ef7701e8779f90eaca37150e40f6 Mon Sep 17 00:00:00 2001 From: Herb Sutter Date: Thu, 1 Oct 2026 13:15:54 -0700 Subject: [PATCH] Apply Oct 1 editors call suggestion Link: https://github.com/isocpp/CppCoreGuidelines/pull/2337#issuecomment-5934406823 --- CppCoreGuidelines.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 34addb87f..beb3e10a8 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -5898,7 +5898,7 @@ Using default member initializers lets the compiler generate the function for yo ##### Enforcement -(Simple) Flag if a default constructor's explicit member initializer is a constant, and recommend that the constant should be written as a data member initializer instead. +(Simple) Flag if a default constructor only initializes members, and recommend that the initializers should be written as data member initializers instead and the compiler-generated default constructor used ### C.46: By default, declare single-argument constructors explicit @@ -6010,6 +6010,8 @@ How would a maintainer know whether `j` was deliberately uninitialized (probably * (Simple) Every constructor should initialize every data member (either explicitly, via a delegating ctor call or via default construction). * (Simple) Default arguments to constructors suggest a default member initializer might be more appropriate. +* (Simple) Flag if a default constructor's explicit member initializer is a constant, and recommend that the constant should be written as a data member initializer instead. + ### C.49: Prefer initialization to assignment in constructors