P2547R0 briefly summarised all the existing customisation point techniques and proposed language features to support writing customisation points. It is definitely the right direction and indeed simplifies the process of authoring customisation points as well as making it more compiler friendly. However, I’d like to add a little bit more.

The story starts from the following code

If you are building your projects on multiple platforms, you probably noticed that on mac with XCode 12, -Wrange-loop-analysis is set on by default, which might cause some code to break if you use -Werror.

Looking at the code I’ve been written in the past, I found that lot’s of lines started with const auto&. Well, I am not going to debate on whether you should use auto const& instead.

Following up my previous post, there are some arguments saying that I should just write a wrapper of the std types. OK, let’s do it.

There are lots of ways of doing customisation points in C++. What is the best way to do customisation points to allow types (or aliases to types) in std namespace? Should we ever allow it?

Next you can update your site name, avatar and other options using the _config.yml file in the root of your repository (shown below).