{"id":33169,"date":"2023-11-14T18:05:41","date_gmt":"2023-11-14T18:05:41","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=33169"},"modified":"2023-11-14T18:05:41","modified_gmt":"2023-11-14T18:05:41","slug":"whats-new-for-cpp-developers-in-visual-studio-2022-17-8","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/whats-new-for-cpp-developers-in-visual-studio-2022-17-8\/","title":{"rendered":"What\u2019s New for C++ Developers in Visual Studio 2022 17.8"},"content":{"rendered":"

We are happy to announce that Visual Studio 2022 version 17.8 is now generally available! This post summarizes the new features you can find in this release for C++. You can download Visual Studio 2022 from the\u00a0Visual Studio downloads page\u00a0<\/a>or upgrade your existing installation by following the\u00a0Update Visual Studio Learn page<\/a>.<\/p>\n

Standard Library<\/h2>\n

The Standard Library Modules standardized in C++23 are now available in C++20 mode. This is a cross-vendor extension, planned or supported also by libstdc++<\/a> and libc++<\/a>.<\/p>\n

We have also implemented several new C++23 and C++26 features, including augmented support for Freestanding implementations and support for std::stacktrace<\/code> in std::format<\/code>. Read all the details in the STL Changelog<\/a>.<\/p>\n

Core Editor<\/h2>\n

Create a Pull Request<\/h2>\n

You can now create a Pull Request directly in Visual Studio. Enter the New Pull Request window by clicking the link in the notification banner in Git Changes after pushing, or from the top-level menu via Git > GitHub\/Azure DevOps > New Pull Request.<\/p>\n

\"A<\/p>\n

Summary Diff<\/h2>\n

Leverage the new summary difference view to focus on the changes in your code.<\/p>\n

\"A<\/p>\n

Enabled in every comparison view, the new summary difference view allows you to toggle the context lines to do file comparison faster.<\/p>\n

Productivity<\/h2>\n

Structured Diagnostics<\/h2>\n

Massive compiler errors which seem impossible to navigate are the bane of many C++ developers\u2019 lives. It\u2019s up to tools to provide a better experience to help you comprehend diagnostics and understand how to fix the root issue.<\/p>\n

To aid this, you can now view structured diagnostics in the Output window and new Problem Details window. Error List entries which have additional information available will show an icon in the new Details column.<\/p>\n

\"A<\/p>\n

Clicking this will open these details in the Problem Details window, allowing you to navigate through the associated information of the error:<\/p>\n

\"A<\/p>\n

This nested structure is also reflected in the Output window:<\/p>\n

1>Source.cpp(18,6):  \r\n1>or 'void pet(_T0)'  \r\n1>Source.cpp(23,5):  \r\n1>the associated constraints are not satisfied  \r\n1>\tSource.cpp(18,10):  \r\n1>\tthe concept 'pettable<lizard>' evaluated to false  \r\n1>\t\tSource.cpp(16,20):  \r\n1>\t\tthe concept 'has_member_pet<lizard>' evaluated to false  \r\n1>\t\t\tSource.cpp(10,44):  \r\n1>\t\t\t'pet': is not a member of 'lizard'  \r\n1>\t\t\tSource.cpp(20,8):  \r\n1>\t\t\tsee declaration of 'lizard'  \r\n1>\t\tSource.cpp(16,41):  \r\n1>\t\tthe concept 'has_default_pet<lizard>' evaluated to false  \r\n1>\t\t\tSource.cpp(13,30):  \r\n1>\t\t\t'is_pettable': is not a member of 'lizard'  \r\n1>\t\t\tSource.cpp(20,8):  \r\n1>\t\t\tsee declaration of 'lizard' \r\n<\/code><\/pre>\n
Find out more about this feature at Structured Diagnostics in the New Problem Details Window.<\/a><\/p>\n
Size and Alignment of Classes, Structs, and Unions<\/h2>\n
Based on feedback from you, we have introduced a Size and Alignment feature. This feature enables you to visualize the size and alignment of your classes, structs, unions, base types, or enums even before the code is compiled. To check the size and alignment, hover over the identifier and a Quick Info tooltip will display the information.<\/p>\n
\"A<\/p>\n
Make Member Function Const<\/h2>\n
We have introduced\u00a0a feature that suggests that you make member functions const<\/code> when they don\u2019t modify the object\u2019s state. You can hover over a member function and click the light bulb icon to quickly access the suggestion and mark the function as const.<\/p>\n
\"A<\/p>\n
This feature is enabled by default as a suggestion. You can configure its settings by navigating to Tools > Options > Text Editor > C\/C++ > Code Style > Linter.<\/p>\n
\"A<\/p>\n
Make Global Function Static<\/h2>\n
Visual Studio now prompts you to mark global functions as static<\/code>. When you encounter a global function lacking a forward declaration, Visual Studio will provide a suggestion, symbolized by a screwdriver icon.<\/p>\n
\"A<\/p>\n
You can adjust the settings for this feature under Tools > Options > Text Editor > C\/C++ > IntelliSense. To learn more about this feature and Make Member Function Const, check out our Make Member Function const and Global Function Static in Visual Studio Blog.<\/a><\/p>\n
Clean Up and Sort #include Directives<\/h2>\n
You can now sort and clean up your #include<\/code> directives automatically.<\/p>\n
Unused #include<\/code> directives will be dimmed in the editor. You can hover over a dimmed include and use the lightbulb menu to either remove that include or all unused includes.<\/p>\n
\"A<\/p>\n
There is now also the option to add #include<\/code> directives for entities which are currently indirectly included via other headers. For example, if you use std::string<\/code> in your code but don\u2019t #include <string><\/code>, the code will still work if some other header you include transitively includes the correct header. This makes the code fragile to changes in other headers. If #include<\/code> cleanup detects indirect headers, a quick action (indicated by three dots in the default view) will appear. Hovering over it will inform you that content from that transitive include is being used. Then, you have the option to either add the direct include individually or add all transitively used includes.<\/p>\n
\"A<\/p>\n
Find out more about this feature at Clean up C\/C++ #includes in Visual Studio<\/a>.<\/p>\n
To automatically sort #includes<\/code>, right-click on any #include<\/code> statement. Then, hovering over the #include<\/code> directives option in the context menu will reveal “Sort #include directives.”<\/p>\n
\"A<\/p>\n
You can also configure transitive include cleanups and include sorting through the Code Cleanup entry. First, open the Code Cleanup configuration menu through Analyze > Code Cleanup > Configure Code Cleanup, or by clicking the arrow next to the broom icon in the bottom status bar and selecting Configure Code Cleanup. Add the desired features to the Included fixers section, then click the broom icon to run them.<\/p>\n
\"A<\/p>\n
You can configure include cleanup and sorting at Tools > Options > Text Editor > C\/C++ > Code Cleanup.<\/p>\n
\"A<\/p>\n
Game Development<\/h2>\n
Unreal Engine Test Adapter<\/h2>\n
Special thanks to the folks at Rare who contributed tremendously to this feature.<\/em><\/p>\n
Streamline your testing process without leaving the IDE with Unreal Engine Test Adapter<\/strong>. You can now discover, run, manage, and debug your Unreal Engine tests. In Visual Studio 2022 version 17.8, your Unreal Engine tests will automatically show up when you open Visual Studio. To see your tests, you can open Test Explorer with View > Test Explorer.<\/p>\n
\"A<\/p>\n
The latest version of our free Visual Studio Tools for Unreal Engine<\/a> is required to use Unreal Engine Test Adapter. In addition, ensure the \u201cUnreal Engine Test Adapter\u201d component in the \u201cGame development with C++\u201d workload is enabled in the Visual Studio Installer.<\/p>\n
Unreal Engine Code Snippets<\/h2>\n
Write code more efficiently with Unreal Engine Code Snippets<\/strong>. In Visual Studio 2022 version 17.8, you can find common Unreal Engine constructs as snippets in your member list. To get started, type any Unreal Engine construct name, for example uclass<\/code>. Press Tab or Enter to expand the snippet.<\/p>\n
\"A<\/p>\n
We have also included exported versions of UCLASS<\/code> (uclass<\/code>, uclassexported<\/code>), UINTERFACE<\/code> (uinterface<\/code>, uinterfaceexported<\/code>), and USTRUCT<\/code> (ustruct<\/code>, ustructexported<\/code>) for those working with exported APIs and plugins. In addition, we have included macros such as SWidget<\/code> (swidget<\/code>), TActorRange<\/code> (tactorrange<\/code>), TObjectRange<\/code> (tobjectrange<\/code>), and WITH_EDITOR<\/code> (witheditor<\/code>) based on your feedback.<\/p>\n
List of Supported Snippets<\/p>\n