This repository has been archived by the owner on Jun 23, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
C++14 has many advantages over C++11, and now it's fully mature for nearly three years. Besides, there's no difficulty for our current codebase to move onto C++14. What we need to do is to upgrade our least compiler support to gcc-5 (suggested GCC-5.5).
The first benefit is that we are no longer suffering from the bug of
std::regex
lib in gcc-4.9, so no need forboost::regex
then.New features introduced in C++14 can be found in https://www.wikiwand.com/en/C%2B%2B14, some by far are useful for us:
std::make_unique
: will replacedsn::make_unique
dsn/utility/chrono_literals.h