October 25, Pavia, Italy
November 6-8, Berlin, Germany
November 3-8, Kona, HI, USA
By Marco Arena | Dec 11, 2017 11:55 AM | Tags: community
My report on the last C++ event we organized in Italy:
C++ Day 2017
by Marco Arena
From the article:
At the beginning of December, on the 2nd, the Italian C++ Community hosted the C++ Day 2017 and about 110 people gather together...
By bfilipek | Dec 7, 2017 11:35 AM | Tags: None
Slides from a talk about C++17 features
Summary of C++17 features
by Bartlomiej Filipek
From the article:
How do you see the new C++ standard? Is it ok? Great? Meh? See my slides from the talk where I tried to answer this question.
By bfilipek | Dec 6, 2017 10:51 AM | Tags: basics
Examples where unique_ptr shines:
5 ways how unique_ptr enhances resource safety in your code
by Bartlomiej Filipek
From the article:
While shared_ptr and weak_ptr are more complex, unique_ptr seems to be a perfect replacement for owning raw pointers. Not to mention is the fact that this pointer type is mostly a compile time “wrapper” and it cost almost nothing in the runtime.
By Adrien Hamelin | Dec 4, 2017 01:54 PM | Tags: c++11 advanced
Your own type predicate
by Andrzej Krzemieński
From the article:
In this post we will see how to define a type trait or a type predicate or a meta-function that would allow us to check at compile time whether a type exposes an interface that we need. That is, we want to check if a given type T has:
- nested typename result_type,
- static member function set_limit that takes one argument of type int,
- member function get_result that returns type const result_type& and that is declared not to throw exceptions...
By Adrien Hamelin | Dec 1, 2017 02:00 PM | Tags: intermediate c++11
Quick A: Yes, as any other virtual member function.
Recently on SO:
May a destructor be final?
May a C++ destructor be declared as final?
Yes.
And if so, does that prevent declaration of a derived class:
Yes, because the derived class would have to declare a destructor (either explicitly by you or implicitly by the compiler), and that destructor would be overriding a function declared final, which is ill-formed.
The rule is [class.virtual]/4:
If a virtual function f in some class B is marked with the virt-specifier final and in a class D derived from B a function D::f overrides B::f, the program is ill-formed.
It's the derivation itself that is ill-formed, it doesn't have to be used.
Is declaring a destructor to be final a workable idiom for indicating that a class is not intended to be used as a base class?
Effectively, but you should just mark the class final. It's quite a bit more explicit.
By Adrien Hamelin | Nov 28, 2017 02:19 PM | Tags: experimental advanced
An article very complete!
C++ Coroutines: Understanding operator co_await
by Lewis Baker
From the article:
In the previous post on Coroutine Theory I described the high-level differences between functions and coroutines but without going into any detail on syntax and semantics of coroutines as described by the C++ Coroutines TS (N4680).
The key new facility that the Coroutines TS adds to the C++ language is the ability to suspend a coroutine, allowing it to be later resumed. The mechanism the TS provides for doing this is via the new co_await operator.
Understanding how the co_await operator works can help to demystify the behaviour of coroutines and how they are suspended and resumed. In this post I will be explaining the mechanics of the co_await operator and introduce the related Awaitable and Awaiter type concepts.
But before I dive into co_await I want to give a brief overview of the Coroutines TS to provide some context...
By Adi | Nov 27, 2017 12:30 PM | Tags: None
Adi Shavit reports from the recent code::dive conference
code::dive Trip Report
by Adi Shavit
From the article:
The code::dive conference took place last week in Poland at the beautiful city of Wrocław (pronounced VROWTS-WAF). I had seen excellent videos of talks from previous years and this year promised a roster of distinguished speakers.
I had never been to a C++ conference before and beyond the talks I was looking forward to meeting face-to-face many of my online Slack, Twitter and GitHub friends, followers and followees, as well as many of the speakers whose work I’ve been following online through blogs, repos and videos.
By GarethRichards | Nov 27, 2017 12:29 PM | Tags: None
Learning about Machine learning with C++.
Machine Learning with C++
by Gareth Richards
From the article:
An introduction to Machine learning demonstrating a how to write a short C++ library which can recognize handwritten digits and implements the standard learning algorithm for neural networks, known as stochastic gradient descent.
By Adrien Hamelin | Nov 24, 2017 02:16 PM | Tags: stl intermediate
And how back_inserter works.
How to Use the STL With Legacy Output Collections
by Jonathan Boccara
From the article:
When you start using the STL and its algorithms in your code, it’s a bit of a change of habits. And then after a while you get used to it. Then it becomes a second nature. And then even your dreams become organized into beautifully structured ranges that fly in and out of well-oiled algorithms.
And when you reach that point, there is no coming back.
Until the day you come upon an old legacy structure that won’t let itself approached by the elegant and expressive way of coding that STL algorithms have. It’s a terrible encounter, where the beast tries to suck you back into the lengthy and dangerous quicksand of the raw for loops that now seemed so far away...
By Adrien Hamelin | Nov 21, 2017 01:13 PM | Tags: community c++20
A thorough and detailed summary of the recent six-day meeting.
Trip Report: C++ Standards Meeting in Albuquerque, November 2017
by Botond Ballo
From the article:
A couple of weeks ago I attended a meeting of the ISO C++ Standards Committee (also known as WG21) in Albuquerque, New Mexico. This was the third committee meeting in 2017; you can find my reports on previous meetings here (February 2017, Kona) and here (July 2017, Toronto). These reports, particularly the Toronto one, provide useful context for this post.
With the final C++17 International Standard (IS) having been voted for publication, this meeting was focused on C++20, and the various Technical Specifications (TS) we have in flight, most notably Modules...