From 3dc1b61ccc4a239191254b4926018ae6fef28d30 Mon Sep 17 00:00:00 2001 From: sankurm Date: Thu, 30 Jun 2022 00:45:17 +0530 Subject: [PATCH 1/2] Issue #1931 - Include C++20 as 'modern C++' --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 15c66d6f3..49e4720e4 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ Many of the guidelines make use of the header-only Guidelines Support Library. O ## Background and scope -The aim of the guidelines is to help people to use modern C++ effectively. By "modern C++" we mean C++11, C++14, and C++17. In other +The aim of the guidelines is to help people to use modern C++ effectively. By "modern C++" we mean C++11, C++14, C++17, and C++20. In other words, what would you like your code to look like in 5 years' time, given that you can start now? In 10 years' time? The guidelines are focused on relatively higher-level issues, such as interfaces, resource management, memory management, and concurrency. Such From 3dce490c389e4cd37c41e0f23808a1c9d23d7f6d Mon Sep 17 00:00:00 2001 From: Ankur Satle Date: Fri, 1 Jul 2022 01:04:05 +0530 Subject: [PATCH 2/2] "modern C++" means C++11 and newer --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 49e4720e4..b26629661 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ Many of the guidelines make use of the header-only Guidelines Support Library. O ## Background and scope -The aim of the guidelines is to help people to use modern C++ effectively. By "modern C++" we mean C++11, C++14, C++17, and C++20. In other +The aim of the guidelines is to help people to use modern C++ effectively. By "modern C++" we mean C++11 and newer. In other words, what would you like your code to look like in 5 years' time, given that you can start now? In 10 years' time? The guidelines are focused on relatively higher-level issues, such as interfaces, resource management, memory management, and concurrency. Such