From 1634e898b66750939eb5a52c97fdc10cb7412419 Mon Sep 17 00:00:00 2001 From: Chris Cotter Date: Thu, 22 Jun 2023 12:25:52 -0400 Subject: [PATCH] C++20 is more up to date than C++17 (#2085) --- CppCoreGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 71bf648..2ad06fd 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -241,7 +241,7 @@ All C++ programmers. This includes [programmers who might consider C](#S-cpl). ## In.aims: Aims -The purpose of this document is to help developers to adopt modern C++ (currently C++17) and to achieve a more uniform style across code bases. +The purpose of this document is to help developers to adopt modern C++ (currently C++20 and C++17) and to achieve a more uniform style across code bases. We do not suffer the delusion that every one of these rules can be effectively applied to every code base. Upgrading old systems is hard. However, we do believe that a program that uses a rule is less error-prone and more maintainable than one that does not. Often, rules also lead to faster/easier initial development. As far as we can tell, these rules lead to code that performs as well or better than older, more conventional techniques; they are meant to follow the zero-overhead principle ("what you don't use, you don't pay for" or "when you use an abstraction mechanism appropriately, you get at least as good performance as if you had handcoded using lower-level language constructs").