-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Use of C++20 features/extensions #432
Comments
We want to keep things compiling on older compilers. The strategy is to allow c++ 14 features but not higher. |
It would be helpful if we could figure out which minimum compiler version we specifically want to target. The codebase already uses some >= C++17 features, so those sections would need a downgrade to comply with the intended target of C++14. Is the Repology page accurate? |
We have to compile on cpp14 compilers, therefore we should not use moderner breaking forms. Do you have some kind of detailed report showing that the code is not cpp14 compliant anymore? |
Hi Kelson, Thank you for the quick reply. Here are the ones that stood out to me. Line 4 in a65cb01
I also found this https://github.com/openzim/zim-tools/wiki/Repology, but I am not sure if that is up to date. I am just trying to figure out which specific compiler versions are the bare minimum we want to support so it can be documented (and so I can install those versions in a container so I can test locally). Just picking out of that repology list and a cursory internet search: Debian 10 uses GCC 10 |
The
src/zimwriterfs/zimcreatorfs.cpp
file uses designated initializers, which is a c++20 feature. It currently works by relying on compiler c++20-extensions with the c++ standard set to c++17 inmeson.build
.Are there any dependency blockers for just changing the c++ standard version to c++20? If there aren't any blockers I can put in a PR.
The text was updated successfully, but these errors were encountered: