June 16-21, Sofia, Bulgaria
September 13-19, Aurora, CO, USA
October 25, Pavia, Italy
November 6-8, Berlin, Germany
November 3-8, Kona, HI, USA
By Adrien Hamelin | Mar 23, 2021 01:14 PM | Tags: c++20
The series continue.
Creating other types of synchronization objects that can be used with co_await, part 9
by Raymond Chen
From the article:
Last time, we tried to make an awaitable shared mutex, but ran into some problems...
By Marco Arena | Mar 23, 2021 04:42 AM | Tags: community
The Italian C++ Conference 2021 is now putting together its program, and they want you to speak on C++. If you have something to share, check out their
Call for Sessions
by Marco Arena
About the conference:
The Italian C++ Conference 2021 will be online on June 19 and will host live sessions and networking on Remo.
The Italian C++ Conference is the biggest and most successful event organized by the Italian C++ Community and it is an environment where professionals, companies and students meet to share experience about C++ development and practices.
Since the first edition back in 2016, the conference has hosted amazing speakers like Andrei Alexandrescu, Walter Brown, Michael Wong, James McNellis, Bartosz Milewski, Ivan Čukić, Jens Weller, Phil Nash, Anastasia Kazakova, Peter Sommerlad, Rainer Grimm, Marc Goodner, Vittorio Romeo, and many more.
The Italian C++ Conference is put on by the Italian C++ Community and is open to anyone who wishes to be there either as a presenter or an attender.
The event will be free to attend.
The Call for Sessions will close on April 11 at 23:59 CET.
By Adrien Hamelin | Mar 22, 2021 02:02 PM | Tags: c++20
The seris continue.
Creating other types of synchronization objects that can be used with co_await, part 8
by Raymond Chen
From the article:
Our next stop in showing off our library for building awaitable synchronization objects is the shared mutex. This one takes advantage of the “extra data” we had been hiding in our nodes...
By Adrien Hamelin | Mar 22, 2021 02:00 PM | Tags: c++20
C++20
by Rainer Grimm
From the article:
My book C++20 is both: a tutorial and a reference for the C++20 standard. It teaches you C++20 and provides you with the details of this new thrilling C++ standard. The thrilling factor is mainly due to the big four of C++20...
By Adrien Hamelin | Mar 22, 2021 01:55 PM | Tags: c++17
More ways to do what you want.
What C++ Fold Expressions Can Bring to Your Code
by Jonathan Boccara
From the article:
In the previous post we saw how fold expressions work. We saw how to define them, how to control their associativity, and how to handle empty variadic packs in a fold expression...
By Ansel Sermersheim | Mar 21, 2021 12:45 PM | Tags: None
New video on the CopperSpice YouTube Channel:
Mutex + Lock = CsLibGuarded
by Barbara Geller and Ansel Sermersheim
About the video:
Our newest C++ video looks at a better way to lock a mutex. We look at making the data part of the solution. The video walks through several variations of an example to explain why the data, mutex, and lock should be tied together and the benefits that result from this change.
Please take a look and remember to subscribe!
By Legalize Adulthood | Mar 21, 2021 12:44 PM | Tags: None
Utah C++ Programmers has released a new video.
Introduction to OpenCV with VcPkg and CMake
by Richard Thomson
From the video description:
OpenCV (Open Source Computer Vision Library) is an open source computer vision and machine learning software library.
This month, Richard Thomson will give us an introduction to OpenCV and walk us through some examples of using the library. OpenCV is a large library, so not every detail can be presented at once. However, we'll try to get a feel for what it looks like to use components from the library and perform some simple image manipulation tasks.
By Lesley Lai | Mar 21, 2021 12:43 PM | Tags: c++17 c++14
Should we use almost always auto parameters?
Don't automatically use auto parameters in C++
by Lesley Lai
From the article:
Since C++14, we can create lambda expressions that take auto parameters. C++20 generalizes this idea by allowing us to do the same thing for regular functions. With this feature's advent, the programming style where all parameters are auto becomes popular among some C++ programmers. However, I think we should not use it if we had to. The more specific the type of the parameter is, the better.
By Adrien Hamelin | Mar 18, 2021 11:34 AM | Tags: c++20
The series continue.
Creating other types of synchronization objects that can be used with co_await, part 7
by Raymond Chen
From the article:
Our next stop in showing off our library for building awaitable synchronization objects are the mutex and recursive mutex...
By Adrien Hamelin | Mar 18, 2021 11:21 AM | Tags: advanced
Know everything about it.
How C++ Resolves a Function Call
by Jeff Preshing
from the article:
C is a simple language. You’re only allowed to have one function with each name. C++, on the other hand, gives you much more flexibility:
- You can have multiple functions with the same name (overloading).
- You can overload built-in operators like + and ==.
- You can write function templates.
- Namespaces help you avoid naming conflicts.
I like these C++ features. With these features, you can make str1 + str2 return the concatenation of two strings. You can have a pair of 2D points, and another pair of 3D points, and overload dot(a, b) to work with either type. You can have a bunch of array-like classes and write a single sort function template that works with all of them.
But when you take advantage of these features, it’s easy to push things too far. At some point, the compiler might unexpectedly reject your code with errors like:
error C2666: 'String::operator ==': 2 overloads have similar conversions note: could be 'bool String::operator ==(const String &) const' note: or 'built-in C++ operator==(const char *, const char *)' note: while trying to match the argument list '(const String, const char *)'Like many C++ programmers, I’ve struggled with such errors throughout my career. Each time it happened, I would usually scratch my head, search online for a better understanding, then change the code until it compiled. But more recently, while developing a new runtime library for Plywood, I was thwarted by such errors over and over again. It became clear that despite all my previous experience with C++, something was missing from my understanding and I didn’t know what it was.
Fortunately, it’s now 2021 and information about C++ is more comprehensive than ever. Thanks especially to cppreference.com, I now know what was missing from my understanding: a clear picture of the hidden algorithm that runs for every function call at compile time.