Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to C++20: issues to be solved #14734

Open
omoerbeek opened this issue Oct 1, 2024 · 0 comments
Open

Move to C++20: issues to be solved #14734

omoerbeek opened this issue Oct 1, 2024 · 0 comments

Comments

@omoerbeek
Copy link
Member

I did a few experiments to compile our codebase with C++20. These are my findings

  1. el-7, debian-buster: forget it, but these are dead within a month anyway.
  2. Minimum version of boost is 1.54 (due to a c++20 incompatibility). This has consequences for el-8
  3. debian-bullseye needs a more modern compiler (likely clang, as the newest gcc there is version 10, which is too old). It also has a too old boost. This one needs a bit more effort.
  4. ubuntu-focal: both boost and gcc are too old, but it wil be dead in 6 months.
  5. The other platforms seem fine. Though only compile tested, no test of executables.

BRanch has the experiment for el-9, which works now, but the spec file is missing conditions, so it breaks other el builds.

To conclusion at this point is: there are a few nice features in c++20, but there is no pressing need to switch to it. If it does not take too much effort to do debian-bullseye, it is worth the trouble to switch after el-7, debian-buster and ubuntu-focal are dead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant