Overload 140 is now available

By Adrien Hamelin | Aug 21, 2017 12:10 PM | Tags: community

ACCU’s Overload journal of June 2017 is out. It contains the following C++ related articles.

Overload 140 is now available

From the journal:

Editorial: Gnomes and Misnomers.
What's in a name? Frances Buontempo decides some names are better than others.

The Path of the Programmer.
Charles Tolman provides a framework for personal development.

A Usable C++ Dialect that is Safe Against Memory Corruption.
Sergey Ignatchenko continues his investigation of allocators for (Re)Actors.

Metaclasses: Thoughts on Generative C++.
Herb Sutter shows how metaclasses could simplify C++ with minimal library extension.

A C++ Developer Sees Rustlang for the First Time.
Katarzyna Macias provides an introduction to Rust for a C++ developer.

Portable Console I/O via iostreams.
Alf Steinbach describes how his library fixes problems streaming non-ASCII characters in Windows.

A Functional Alternative to Dependency Injection in C++.
Satprem Pamudurthy showcases a functional alternative to dependency injection in C++.

About the C++ Core Guidelines.
Andreas Fertig shows us the C++ core guidelines.

Afterwood.
Chris Oldwood reminds us to fix the problem, not to blame.

Quick Q: Make C++ fail compilation on specific instantiation of template function

By Adrien Hamelin | Aug 18, 2017 12:11 PM | Tags: intermediate c++11

Quick Q: Delete its constructor

Recently on SO:

Make C++ fail compilation on specific instantiation of template function

Since foo is a complete specialization, it will always get compiled, and the static assert will always get called.

However, there’s an easier way:

template <>
Bar foo<Bar>(Bar val) = delete;

This will say that this specific version is deleted, and cannot be called.

Ranges, Coroutines, and React: Early Musings on the Future of Async in C++ -- Eric Niebler

By Eric Niebler | Aug 17, 2017 03:56 PM | Tags: intermediate experimental c++20

Eric Niebler shares his thoughts about the interaction of ranges and co-routines in his recent blog post.

Ranges, Coroutines, and React: Early Musings on the Future of Async in C++

by Eric Niebler

From the article:

Another way to look at this is that synchronous ranges are an example of a pull-based interface: the user extracts elements from the range and processes them one at a time. Asynchronous ranges, on the other hand, represent more of a push-based model: things happen when data shows up, whenever that may be. This is akin to the reactive style of programming.

By using ranges and coroutines together, we unify push and pull based idioms into a consistent, functional style of programming. And that’s going to be important, I think.

Your own error condition--Andrzej Krzemieński

By Adrien Hamelin | Aug 15, 2017 01:51 PM | Tags: intermediate c++11

The series continues.

Your own error condition

by Andrzej Krzemieński

From the article:

In the previous post we have seen how you can create your own error-code enumeration for representing different reasons for failure in your component, and how you can store them and convey them type erased via std::error_code. In this post we will see how you can inspect an error situation encoded in std::error_code, and how you can build useful queries about error conditions.

7 Features of C++17 that will simplify your code--fenbf

By Adrien Hamelin | Aug 14, 2017 02:48 PM | Tags: c++17 basics

C++17 is almost there.

7 Features of C++17 that will simplify your code

by fenbf

From the article:

With each C++ standard, we aim for simpler, cleaner and more expressive way to code. C++17 offers several "big" language features that should make our code nicer. Today, I tried to pick seven things that make your code more compact right off the bat.

Quick Q: Why are static addresses constexpr?

By Adrien Hamelin | Aug 10, 2017 01:28 PM | Tags: intermediate c++11

Quick A: Because it is defined at compile time in a special section.

Recently on SO:

A little confused about constexpr functions

If 'x' is declared static, there are no errors. Why?

This is because there is always exactly one x in the program. It has an address (somewhere in the .data segment under normal conditions).

Confusingly, both static and extern keywords specify the storage duration as static (they differ in linkage)

How is it possible to get a variable address during the compilation process? Aren't they allocated at run-time?

Variables with automatic, dynamic or thread storage durations are allocated at runtime. Static duration variables are allocated by the compiler. (The linker and OS can change the location, but they know how to fix all the references when they do)

 

C++17: Direct vs Copy List Initialization--Marc Gregoire

By Adrien Hamelin | Aug 10, 2017 01:12 PM | Tags: c++17 basics

C++17 brought many things:

C++17: Direct vs Copy List Initialization

by Marc Gregoire

From the article:

The auto type deduction rules have changes in C++17. With C++17, if you use copy list initialization, then an initializer_list<> is deduced.

The reviews at r/cpp_review have begun!

By Meeting C++ | Aug 10, 2017 08:12 AM | Tags: performance intermediate efficiency community codereview c++14 c++11 basics

Participate in the first two reviews at r/cpp_review:

The reviews have begun

by Jens Weller

From the article

A few weeks ago I announced a C++ review community, which since then has grown to 250+ members on reddit. There has been great feedback and discussions since then, so that the idea is now ready to be tested.  With August, the first review period has started

2017-07 post-Toronto mailing available

By Blog Staff | Aug 8, 2017 09:49 AM | Tags: None

The full 2017-07 mailing of new standards papers is now available.

A Summary of the Metaclasses Proposal for C++

By Adrien Hamelin | Aug 7, 2017 03:39 PM | Tags: experimental community

A revolution!

A Summary of the Metaclasses Proposal for C++

by Jonathan Boccara

From the article:

A couple of weeks ago, Herb Sutter posted his proposal about metaclasses, triggering a wave of enthusiasm among the C++ community. And for good reason.