I have written more than 130 posts in this blog. I covered the topics multithreading, embedded, and functional programming in modern C++. I think a lot of my posts are quite good. Even better than the books I have written. So I had an idea.
The unification of templates, concepts, and placeholders goes on. This time, I will have a closer look at constrained (concepts) and unconstrained (auto) placeholders in the context of templates.
I'm more than happy to say. I'm done with translating my more the 130 posts from http://www.grimm-jaud.de/index.php/blog to http://www.modernescpp.com/index.php. I started in April last year and it took me almost a year to translate my German posts into English. What does this mean for my German and my English blog?
C++11 has with auto unconstrained placeholders. You can use concepts in C++20 as constrained placeholders. What seems at first glimpse not so thrilling is for me the decisive quantum leap. C++ templates will become an easy to use C++ feature.
Task blocks use the well-known fork-join paradigm for the parallel execution of tasks.
Transactional memory is based on the idea of a transaction from the database theory. Transactional memory shall make the handling with threads a lot easier. That for two reasons. Data races and deadlocks disappear. Transactions are composable.
Coroutines are functions that can suspend and resume their execution while keeping their state. The evolution in C++20 goes one step further.
Currently are 129 guests and no members online
Kubik-Rubik Joomla! Extensions