ReSharper C++ 2019.1 is released: Doctest support, more C++17 and C++20 features, and better for UE4

By Anastasia Kazakova | May 6, 2019 06:01 AM | Tags: community c++17

ReSharper C++ 2019.1 is just released! It brings Significant performance boosts, C++17 and C++20 features, support for Doctest, more flexible configuration for C++ naming and Clang-Tidy, and productivity features for Unreal Engine developers.

ReSharper C++ 2019.1: More Responsive, Better for Unreal Engine, and with New Language Features

by Anastasia Kazakova

From the article:

This year’s first major update includes the following changes and improvements:

• Performance improvements, including better start times and quicker navigation actions
• Visual Studio 2019 support
• Unreal Engine 4 support
• More steps towards C++17 and C++20 compliance
• Updated naming and formatter settings
• More flexible Clang-Tidy integration
• Doctest support

Boost 1.70.0 released

By Adrien Hamelin | Apr 12, 2019 12:07 PM | Tags: community boost

Check it out:

Boost 1.70.0 released

From the release notes:

New Libraries​

• Outcome: A set of tools for reporting and handling function failures in contexts where directly using C++ exception handling is unsuitable, from Niall Douglas.
• Histogram: Fast and extensible multi-dimensional histograms with convenient interface for C++14, from Hans Dembinski.

Updated Libraries​

1. Asio:

• Fixed a Windows-specific memory leak that may occur when system_executor is used.
• Improved dispatch, post and defer documentation.
• Fixed compile errors that occur when using the composed read and write operations with MSVC 11.0.
• Fixed a macOS-specific warning about the deprecation of OSMemoryBarrier.
• Changed composed asynchronous read and write operations to move buffer sequence objects.
• Added a fallback error code for when we OpenSSL produces an SSL_ERROR_SYSCALL result without an associated error.
• Suppressed the eof error on SSL shutdown as it actually indicates success.
• Ensured SSL handshake errors are propagated to the peer before the local operation completes.
• Fixed buffer_sequence_begin and buffer_sequence_end to prevent implicit conversion.
• Changed the range-based asynchronous connect operation to deduce the EndpointSequence iterator type.
• Fixed calculation of absolute timeout when the backend uses pthread_cond_timedwait.
• Changed receive operations to return the correct number of bytes transferred when truncation (error::message_size) occurs on a datagram-oriented socket.
• Enabled recycling of the memory used to type-erase a function object with the polymorphic executor.
• Added a new BOOST_ASIO_DISABLE_VISIBILITY configuration #define.
• Added the noexcept qualifier to various functions.
• Added a constructor for local::basic_endpoint that takes a string_view.
• Relaxed the completion condition type requirements to only require move-constructibility rather than copy-constructibility.
• Added a make_strand helper function.
• Added a new async_compose function that simplifies the implementation of user-defined asynchronous operations.
• Added a new DynamicBuffer_v2 concept which is CopyConstructible.
• Updated the Coroutines TS support and promoted it to the asio namespace.
• Added a new async_result form with an initiate static member function.
• Added the ability to use custom I/O executors with I/O objects (such as sockets).
• This release includes a number of new features, bug fixes, performance enhancements, and documentation improvements. Notable changes include:
• Consult the Revision History for further details.

...

CLion 2019.1 release comes with ClangFormat and initial embedded dev support

By Anastasia Kazakova | Mar 28, 2019 08:02 AM | Tags: None

As announced earlier, our main areas of focus this year are IDE performance, expanding Clangd leverage, and Embedded Development. This update makes headway in all three areas.

doctest -- The Fastest C++ Testing Framework -- version 2.3 released! -- Viktor Kirilov

By onqtam | Mar 28, 2019 07:39 AM | Tags: None

doctest brings the ability of compiled languages such as D, Rust and Nim to write tests right next to the production code to C++.

doctest - "The Fastest C++ Testing Framework" - version 2.3 released

by Viktor Kirilov

From the article:

Version 2.3 brings an extensible reporter system and a few already implemented reporters with the framework - most importantly one for XML - vital for Continuous Integration (CI) workflows. Huge thanks to the Catch2 project for paving the way for single header testing libraries.

Bootstrapping a vcpkg-based cmake project in Visual Studio--Sumant Tambe

By Adrien Hamelin | Mar 27, 2019 01:02 PM | Tags: community

You can do it.

Bootstrapping a vcpkg-based cmake project in Visual Studio

by Sumant Tambe

From the article:

After the last week's 2019 Microsoft MVP Summit, I decided to give Microsoft vcpkg a shot. I've a cmake project at work and we target Linux using the Hunter package manager. So vcpkg had been on the back-burner for me...

Turning anything into a fire-and-forget coroutine--Raymond Chen

By Adrien Hamelin | Mar 27, 2019 12:59 PM | Tags: community

One more step.

Turning anything into a fire-and-forget coroutine

by Raymond Chen

From the article:

Last time, we wrote a helper function for converting an awaitable into a winrt::fire_and_forget, as well as another helper function that takes a lambda that returns an awaitable, and which invokes the lambmda as a winrt::fire_and_forget...

Expressing fire-and-forget coroutines more explicitly, -or- How to turn any coroutine into fire-...

By Adrien Hamelin | Mar 26, 2019 10:45 AM | Tags: community

The series continues.

Expressing fire-and-forget coroutines more explicitly, -or- How to turn any coroutine into fire-and-forget

by Raymond Chen

From the article:

Last time, we looked at how to mark a coroutine as fire-and-forget, meaning that the caller does not get any information about when the coroutine completes. This is fine as far as it goes, but it may not be what you want...

winrt::fire_and_forget was too forgetful

By Adrien Hamelin | Mar 26, 2019 10:39 AM | Tags: community

Heard about it?

winrt::fire_and_forget was too forgetful

by Raymond Chen

From the article:

C++/WinRT provides a handy helper class called winrt::fire_and_forget. It lets you specify that nobody is going to observe the result of the coroutine. This is handy because it lets you tell the compiler that the lack of observation is intentional, so it won’t generate a warning...

Game performance and compilation time improvements in Visual Studio 2019--Gratian Lup

By Adrien Hamelin | Mar 21, 2019 12:03 PM | Tags: performance community

Getting better!

Game performance and compilation time improvements in Visual Studio 2019

by Gratian Lup

From the article:

The C++ compiler in Visual Studio 2019 includes several new optimizations and improvements geared towards increasing the performance of games and making game developers more productive by reducing the compilation time of large projects. Although the focus of this blog post is on the game industry, these improvements apply to most C++ applications and C++ developers...

Understanding GCC warnings--Martin Sebor

By Adrien Hamelin | Mar 18, 2019 10:56 AM | Tags: community

In detail.

Understanding GCC warnings

by Martin Sebor

From the article:

Most of us appreciate when our compiler lets us know we made a mistake. Finding coding errors early lets us correct them before they embarrass us in a code review or, worse, turn into bugs that impact our customers. Besides the compulsory errors, many projects enable additional diagnostics by using the -Wall and -Wextra command-line options. For this reason, some projects even turn them into errors via -Werror as their first line of defense. But not every instance of a warning necessarily means the code is buggy. Conversely, the absence of warnings for a piece of code is no guarantee that there are no bugs lurking in it...