{fmt} 8.0 released with compile-time format string checks, compile-time formatting, improved performance and more

by Victor Zverovich

Enabled compile-time format string check by default...

<format> in Visual Studio 2019 version 16.10

by Charlie Barto

C++20 adds a new text formatting facility to the standard library, designed primarily to replace snprintf and friends with a fast and type safe interface. The standardized library is based on the existing {fmt} library, so users of that library will feel at home.

Before diving into how std::format works I want to thank Victor Zverovich, Elnar Dakeshov, Casey Carter, and miscco, all of whom made substantial contributions to this feature, and were the reason why we could complete it so quickly...

PVS-Studio Team: Switching to Clang Improved PVS-Studio C++ Analyzer's Performance

by Alexey Govorov and Sergey Larin

From the earliest days, we used MSVC to compile the PVS-Studio C++ analyzer for Windows - then, in 2006, known as Viva64, version 1.00. With new releases, the analyzer's C++ core learned to work on Linux and macOS, and we modified the project's structure to support CMake. However, we kept using the MSVC compiler to build the analyzer's version for Windows. Then, in 2019, on April 29th, Visual Studio developers announced they had included the LLVM utilities and Clang compiler in the IDE.

PVS-Studio 7.13

by Andrey Karpov

• The C++ analyzer provides enhanced support of Ninja projects on Windows using JSON Compilation Database (compile_commands.json).
• The C++ PVS-Studio analyzer spends 10% less time checking source files with the use of the Clang compiler.
• To check C++ and C# Visual Studio PVS-Studio_Cmd.exe projects, you can pass the suppression file directly. Before this, you could add suppressed warnings only at the projects and solution level.

C++20 Ranges are complete in Visual Studio 2019 version 16.10

by Casey Carter

We are proud to announce completion of our implementation of C++20 Ranges in the Standard Library in the VS2019 v16.10 release under/std:c++latest. We announced the first useful user-visible parts of Ranges in VS 2019 v16.6 in mid 2020, the trickle accelerated into a gushing stream, and the final parts are now in place. This represents a huge body of work with input from multiple open-source contributors over the last two years...

Building LLVM in 90 seconds using Amazon Lambda

by Nelson Elhage

Last week, Frederic Cambus wrote about building LLVM quickly on some very large machines, culminating in a 2m37s build on a 160-core ARM machine.

I don’t have a giant ARM behemoth, but I have been working on a tool I call Llama, which lets you offload computational work – including C and C++ builds – onto Amazon Lambda. I decided to see how good it could do at a similar build...

What’s Next: A Roadmap for CLion 2021.2

by Anastasia Kazakova

CLion 2021.1 is now released along with the first bug-fix update 2021.1.1 addressing some of the most critical issues which unfortunately squeezed through our testing procedures. We do hope you are enjoying the update now and giving the new data flow analysis, Makefile and dynamic analysis in remote mode, and C/C++ postfix completion a try. We are listening to your feedback carefully and planning the upcoming bug-fix updates accordingly. It’s also time to move forward and see what CLion 2021.2 may look like!

All vcpkg enterprise features now generally available: versioning, binary caching, manifests and registries

by Augustin Popa

We are announcing today that all major vcpkg enterprise features are no longer experimental. The latest vcpkg release makes versioning, binary caching, manifests and registries generally available to any developer, team or enterprise...

New Static Analysis Rule for Bounds Checking

by Jordan Maples

We have added a new experimental static analysis rule in Visual Studio 16.10 version Preview 3 – C26458, WARNING_PATH_SENSITIVE_USE_GSL_AT. The new warning is a more precise and less noisy version of warning C26446, WARNING_USE_GSL_AT. Both warnings analyse standard containers for unchecked element access and they both share the warning message: “Prefer to use gsl::at() instead of unchecked subscript operator (bounds.4).” This new warning, however, uses path sensitive analysis to track buffer size validation calls to provide a less noisy, more targeted warning compared to C26446...

Visual Studio 2019 v16.10 Preview Release Notes

The Visual Studio 2019 Blog is the official source of product insight from the Visual Studio Engineering Team. You can find in-depth information about the Visual Studio 2019 releases in the following posts...