March 11-13, Online
March 16-18, Madrid, Spain
March 23-28, Croydon, London, UK
March 30, Kortrijk, Belgium
May 4-8, Aspen, CO, USA
May 4-8, Toronto, Canada
June 8 to 13, Brno, Czechia
June 17-20, Folkestone, UK
September 12-18, Aurora, CO, USA
November 6-8, Berlin, Germany
November 16-21, Búzios, Rio De Janeiro, Brazil
By Adrien Hamelin | Jun 12, 2018 12:31 PM | Tags: c++17 basics
Spreading the knowledge.
Modern C++ Features – std::optional
by Arne Mertz
From the article:
Sometimes we want to express the state of “nothing meaningful” instead of a value. This is the use case for C++17’s std::optional...
By Adrien Hamelin | Jun 8, 2018 12:32 PM | Tags: community
Were you there?
Triple trip report from ACCU, C++ Russia and C++Now 2018 – Part 1
by Jonathan Boccara
From the article:
Going to conferences is a great experience, to learn about your domain and meet people that work in it. Going to conferences can give you tools to write better code.
I’ve had the chance to go to (and speak at) three conferences over a month:
- ACCU in Bristol, UK at the beginning of April,
- C++ Russia in Saint-Petersburg, Russia in mid April,
- C++Now in Aspen, US at the beginning of May.
I haven’t seen many people attending all three of them, so I figured I could make a combined trip report, to give you an idea of what they’re like. And more importantly what you would get by attending either one.
And a huge thanks to the company I work for, Murex, for sending me all over the world of C++!
By Adrien Hamelin | Jun 8, 2018 12:28 PM | Tags: c++17 basics
Simple and useful.
C++17: std::string_view
by Marc Gregoire
From the article:
If you have to write a function that accepts a string, what type of parameter will you use?
By Adrien Hamelin | Jun 6, 2018 12:06 PM | Tags: c++17 advanced
Really everything!
Everything You Need to Know About std::variant from C++17
by Bartlomiej Filipek
From the article:
Around the time C++17 was being standardized I saw magical terms like “discriminated union”, “type-safe union” or “sum type” floating around. Later it appeared to mean the same type: “variant”...
By Adrien Hamelin | Jun 6, 2018 11:43 AM | Tags: c++17 basics
Simple and useful.
C++17: Fallthrough in switch statements
by Marc Gregoire
From the article:
A C++ switch statement allows execution to fall through from one case to the next case when a break statement is missing...
By Meeting C++ | Jun 5, 2018 08:12 AM | Tags: meetingcpp community
Lots of User Groups are meeting in June, Meeting C++ has posted an detailed overview:
C++ User Group Meetings in June 2018
by Jens Weller
From the article:
The monthly overview of upcoming C++ User Group meetings. Join a C++ User Group near you, or learn how to start your own!
There are 4 new C++ User Groups: Houston, Prague, Cluj, New York.
By Adrien Hamelin | Jun 4, 2018 01:38 PM | Tags: c++17 basics
Do you know it?
C++17: std::byte
by Marc Gregoire
From the article:
C++17 introduced a new type: std::byte...
By Adrien Hamelin | Jun 4, 2018 01:19 PM | Tags: experimental
Nothing is easy.
App-level Developer on std::error Exceptions Proposal for C++. Part II. The Discussion.
by "No Bugs" Hare
From the article:
For quite a long while, in certain parts of C++ community, there is a substantial resistance to existing C++ exceptions; this leads to an alternative subculture of using error codes instead of exceptions, so there are effectively two barely-compatible C++ worlds: world-using-exceptions, and world-using-error-codes...
By Adrien Hamelin | Jun 4, 2018 12:57 PM | Tags: experimental
Talking about the future.
App-level Developer on std::error Exceptions Proposal for C++. Part I. The Good
by "No Bugs" Hare
From the article:
Very recently (that’s less than 3 weeks ago) a very audacious proposal was published by no less than Herb Sutter, under the name of [P0709R0]...
By shreck | Jun 3, 2018 01:07 AM | Tags: None
An updated discussion on C++ type design, especially the overlap between Regular and reference types.
Revisiting Regular Types
By Titus Winters
From the article:
With 20 years of experience, we know that Regular type design is a good pattern - we should model user-defined types based on the syntax and semantics of built-in types where possible. However, common formulations of Regular type semantics only apply to values, and for performance reasons we commonly pass by reference in C++. In order to use such a reference as if it were its underlying Regular type we need some structural knowledge of the program to guarantee that the type isn’t being concurrently accessed. Using similar structural knowledge, we can treat some non-Regular types as if they were Regular, including reference types which don’t own their data. Under such an analysis, string_view indeed behaves as if it were Regular when applied to common usage (as a parameter). However, span does not, and further it is (currently) impossible to have shallow copy, deep compare, and Regular const semantics in the same type in C++.
This analysis provides us some basis to evaluate non-owning reference parameters types (like string_view and span) in a practical fashion, without discarding Regular design.