The C++ Core Guidelines are a portable set of guidelines, rules, and best practices about coding in C++ created by C++ experts and designers. Visual Studio currently supports a subset of these rules as part of its Microsoft C++ Code Analysis tools. The core guideline checkers are installed by default in Visual Studio 2017 and Visual Studio 2019. They'reavailable as a NuGet package for Visual Studio 2015.

The C++ Core Guidelines Project

Created by Bjarne Stroustrup and others, the C++ Core Guidelines are a guide to using modern C++ safely and effectively. The Guidelines emphasize static type safety and resource safety. They identify ways to eliminate or minimize the most error-prone parts of the language. They also suggest how to make your code simpler, more reliable, and have better performance. These guidelines are maintained by the Standard C++ Foundation. To learn more, see the documentation,C++ Core Guidelines, and access the C++ Core Guidelines documentation project files onGitHub.

Enable the C++ Core Check guidelines in Code Analysis

Examples

Here's an example of some of the issues that the C++ Core Check rules can find:

// CoreCheckExample.cpp// Add CppCoreCheck package and enable code analysis in build for warnings.int main(){    int arr[10];           // warning C26494    int* p = arr;          // warning C26485    [[gsl::suppress("bounds.1", justification : "This attribute suppresses Bounds rules #1")]]    {        int* q = p + 1;    // warning C26481 (suppressed)        p = q++;           // warning C26481 (suppressed)    }    return 0;}

This example demonstrates a few of the warnings that the C++ Core Check rules can find:

• C26494 is rule Type.5: Always initialize an object.

• C26485 is rule Bounds.3: No array-to-pointer decay.

• C26481 is rule Bounds.1: Don't use pointer arithmetic. Usespan instead.

Install and enable the C++ Core Check code analysis rulesets, then compile this code. Code analysis outputs the first two warnings, and suppresses the third. Here's the build output from the example code in Visual Studio 2015:

1>------ Build started: Project: CoreCheckExample, Configuration: Debug Win32 ------1>  CoreCheckExample.cpp1>  CoreCheckExample.vcxproj -> C:\Users\username\documents\visual studio 2015\Projects\CoreCheckExample\Debug\CoreCheckExample.exe1>  CoreCheckExample.vcxproj -> C:\Users\username\documents\visual studio 2015\Projects\CoreCheckExample\Debug\CoreCheckExample.pdb (Full PDB)c:\users\username\documents\visual studio 2015\projects\corecheckexample\corecheckexample\corecheckexample.cpp(6): warning C26494: Variable 'arr' is uninitialized. Always initialize an object. (type.5: http://go.microsoft.com/fwlink/p/?LinkID=620421)c:\users\username\documents\visual studio 2015\projects\corecheckexample\corecheckexample\corecheckexample.cpp(7): warning C26485: Expression 'arr': No array to pointer decay. (bounds.3: http://go.microsoft.com/fwlink/p/?LinkID=620415)========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

The C++ Core Guidelines are there to help you write better and safer code. However, you might find an instance where a rule or a profile shouldn't be applied. It's easy to suppress it directly in the code. You can use the[[gsl::suppress]] attribute to keep C++ Core Check from detecting and reporting any violation of a rule in the following code block. You can mark individual statements to suppress specific rules. You can even suppress the entire bounds profile by writing[[gsl::suppress("bounds")]] without including a specific rule number.

Supported rule sets

As new rules are added to the C++ Core Guidelines Checker, the number of warnings that are produced for pre-existing code might increase. You can use predefined rule sets to filter which kinds of rules to enable. You'll find reference articles for most rules underVisual Studio C++ Core Check Reference.

• Arithmetic Rules: Rules to detect arithmeticoverflow,signed-unsigned operations, andbit manipulation.^15.6

• Bounds Rules: Enforce theBounds profile of the C++ Core Guidelines.^15.3

• Class Rules: A few rules that focus on proper use of special member functions and virtual specifications. They're a subset of the checks recommended forclasses and class hierarchies.^15.5

• Concurrency Rules: A single rule, which catches bad guard object declarations. For more information, seeguidelines related to concurrency.^15.5

• Const Rules: Enforceconst-related checks from the C++ Core Guidelines.^15.3

• Declaration Rules: A couple of rules from theinterfaces guidelines that focus on how global variables are declared.^15.5

• Enum Rules: These rules enforceenum-related checks from the C++ Core Guidelines.^16.3

• Experimental Rules These are experimental C++ Core Check rules that are useful but not ready for everyday use. Try them out andprovide feedback.^16.0

• Function Rules: Two checks that help with adoption of thenoexcept specifier. They're part of the guidelines forclear function design and implementation.^15.5

• GSL Rules: These rules enforce checks related to theGuidelines Support Library from the C++ Core Guidelines.^15.7

• Lifetime Rules: These rules enforce theLifetime profile of the C++ Core Guidelines.^15.7

• Owner Pointer Rules: Enforceresource-management checks related to owner<T> from the C++ Core Guidelines.^15.3

• Raw Pointer Rules: Enforceresource-management checks related to raw pointers from the C++ Core Guidelines.^15.3

• Shared pointer Rules: It's part ofresource management guidelines enforcement.^15.5 We added a few rules specific to how shared pointers are passed into functions or used locally.

• STL Rules: These rules enforce checks related to theC++ Standard Library (STL) from the C++ Core Guidelines.^15.7

• Style Rules: One simple but important check, which bans use ofgoto.^15.5 It's the first step to improve your coding style and use of expressions and statements in C++.

• Type Rules: Enforce theType profile of the C++ Core Guidelines.^15.3

• Unique Pointer Rules: Enforceresource-management checks related to types with unique pointer semantics from the C++ Core Guidelines.^15.3

• C++ Core Check Rules: This rule set contains all the currently implemented checks from theC++ Core Guidelines, except for the Experimental rules.

^15.3 These rules first appeared in Visual Studio 2017 version 15.3
^15.5 These rules first appeared in Visual Studio 2017 version 15.5
^15.6 These rules first appeared in Visual Studio 2017 version 15.6
^15.7 These rules first appeared in Visual Studio 2017 version 15.7
^16.0 These rules first appeared in Visual Studio 2019 version 16.0
^16.3 These rules first appeared in Visual Studio 2019 version 16.3

You can choose to limit warnings to just one or a few of the groups. TheNative Minimum andNative Recommended rule sets include C++ Core Check rules and other PREfast checks.

Macros

The C++ Core Guidelines Checker comes with a header file, which defines macros that make it easier to suppress entire categories of warnings in code:

ALL_CPPCORECHECK_WARNINGSCPPCORECHECK_TYPE_WARNINGSCPPCORECHECK_RAW_POINTER_WARNINGSCPPCORECHECK_CONST_WARNINGSCPPCORECHECK_OWNER_POINTER_WARNINGSCPPCORECHECK_UNIQUE_POINTER_WARNINGSCPPCORECHECK_BOUNDS_WARNINGS

These macros correspond to the rule sets and expand into a space-separated list of warning numbers. By using the appropriate pragma constructs, you can configure the effective set of rules that is interesting for a project or a section of code. In the following example, code analysis warns only about missing constant modifiers:

#include <CppCoreCheck\Warnings.h>#pragma warning(disable: ALL_CPPCORECHECK_WARNINGS)#pragma warning(default: CPPCORECHECK_CONST_WARNINGS)

Attributes

The Microsoft C++ compiler has limited support for the[[gsl::suppress]] attribute. It can be used to suppress warnings on expression and block statements inside functions.

// Suppress only warnings from the 'r.11' rule in expression.[[gsl::suppress("r.11")]] new int;// Suppress all warnings from the 'r' rule group (resource management) in block.[[gsl::suppress("r")]]{    new int;}// Suppress only one specific warning number.// For declarations, you might need to use the surrounding block.// Macros are not expanded inside of attributes.// Use plain numbers instead of macros from the warnings.h.[[gsl::suppress("26400")]]{    int *p = new int;}

Suppress analysis by using command-line options

Instead of #pragmas, you can use command-line options in the file's property page to suppress warnings for a project or a single file. For example, to disable the warning C26400 for a file:

1. Right-click the file inSolution Explorer and chooseProperties.

2. In theProperty Pages dialog box, select theConfiguration Properties >C/C++ >Command Line property page.

3. In theAdditional Options edit box, add/wd26400.

You can use the command-line option to temporarily disable all code analysis for a file by specifying/analyze-. You'll see warningD9025 overriding '/analyze' with '/analyze-', which reminds you to re-enable code analysis later.

Enable the C++ Core Guidelines Checker on specific project files

Sometimes it's useful to do focused code analysis and still use the Visual Studio IDE. Try the following sample scenario for large projects. It can save build time and make it easier to filter results:

1. In the command shell, set theesp.extension environment variable.

2. To inherit this variable, open Visual Studio from the command shell.

3. Load your project and open its properties.

4. Enable code analysis, pick the appropriate rule sets, but don't enable code analysis extensions.

5. Go to the file you want to analyze with the C++ Core Guidelines Checker and open its properties.

6. ChooseConfiguration Properties >C/C++ >Command Line >Additional Options and add/analyze:plugin EspXEngine.dll

7. Disable the use of precompiled header (Configuration Properties >C/C++ >Precompiled Headers). It's necessary because the extensions engine might attempt to read its internal information from the precompiled header (PCH). If the PCH was compiled with default project options, it won't be compatible.

8. Rebuild the project. The common PREFast checks should run on all files. Because the C++ Core Guidelines Checker isn't enabled by default, it should only run on the file that's configured to use it.

How to use the C++ Core Guidelines Checker outside of Visual Studio

You can use the C++ Core Guidelines checks in automated builds.

MSBuild

The Native Code Analysis checker (PREfast) is integrated into MSBuild environment by custom targets files. You can use project properties to enable it, and add the C++ Core Guidelines Checker (which is based on PREfast):

  <PropertyGroup>    <EnableCppCoreCheck>true</EnableCppCoreCheck>    <CodeAnalysisRuleSet>CppCoreCheckRules.ruleset</CodeAnalysisRuleSet>    <RunCodeAnalysis>true</RunCodeAnalysis>  </PropertyGroup>

Make sure you add these properties before the import of theMicrosoft.Cpp.targets file. You can pick specific rule sets or create a custom rule set. Or, use the default rule set that includes other PREfast checks.

You can run the C++ Core Checker only on specified files. Use the same approach asdescribed earlier, but use MSBuild files. The environment variables can be set by using theBuildMacro item:

<ItemGroup>    <BuildMacro Include="Esp_Extensions">      <EnvironmentVariable>true</EnvironmentVariable>      <Value>CppCoreCheck.dll</Value>    </BuildMacro></ItemGroup>

If you don't want to modify the project file, you can pass properties on the command line:

msbuild /p:EnableCppCoreCheck=true /p:RunCodeAnalysis=true /p:CodeAnalysisRuleSet=CppCoreCheckRules.ruleset ...

Non-MSBuild projects

If you use a build system that doesn't rely on MSBuild, you can still run the checker. To use it, you need to get familiar with some internals of the Code Analysis engine configuration. We don't guarantee support for these internals in future versions of Visual Studio.

Code Analysis requires a few environment variables and compiler command-line options. We recommend you use theNative Tools Command Prompt environment so you don't have to search for specific paths for the compiler, include directories, and so on.

• Environment variables

  • set esp.extensions=cppcorecheck.dll This tells the engine to load the C++ Core Guidelines module.
  • Since Visual Studio 2019 we no longer recommend setting theesp.annotationbuildlevel environment variable because setting it can result in false positives. If seeing unexpected results, remove this variable from your environment.
  • set caexcludepath=%include% We highly recommend that you disable warnings that fire on standard headers. You can add more paths here, for example the path to the common headers in your project.

• Command-line options

  • /analyze Enables code analysis (consider also using/analyze:only and/analyze:quiet).
  • /analyze:plugin EspXEngine.dll This option loads the Code Analysis Extensions engine into the PREfast. This engine, in turn, loads the C++ Core Guidelines Checker.

Use the Guideline Support Library

The Guideline Support Library (GSL) is designed to help you follow the Core Guidelines. The GSL includes definitions that let you replace error-prone constructs with safer alternatives. For example, you can replace aT*, length pair of parameters with thespan<T> type. The GSL project is available on GitHub athttps://github.com/Microsoft/GSL. The library is open-source, so you can view the sources, make comments, or contribute. You can also use thevcpkg package manager to download and install the library locally.

See also

• Visual Studio C++ Core Check Reference