-
Notifications
You must be signed in to change notification settings - Fork 40
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
Any support for older C++ standards? #1258
Comments
@gpicciuca QLever makes quite extensive use of modern C++ because it makes the code much cleaner, safer, and more maintainable. Of course, it would be possible to write code that realizes the features we use from C++17 and C++20 based on C++14. If you want to try it, we are happy to support you, but we do not have the capacity to do this ourselves. Out of curiosity: How long will you be bound by this restriction? |
Sorry for the late response. I double checked and we can actually use C++17 as of latest but C++20 is still far as there are internal procedures (auditing, etc) for new features to be allowed into the Automotive domain (mainly related, but not limited, to MISRA compliance). MISRA23 was released recently which covers C++17 only so I can't really give you a precise answer for when C++20 will be accepted. |
Hello,
Is there any chance that QLever may support older, more "mature" C++ standards? We're looking for a modern C++ knowledge graph solution which supports RDF and semantic reasoning, but are restricted to C++14 at best (GCC9, CLang15), and we're unable to change these restrictions as per project requirements (automotive area).
The text was updated successfully, but these errors were encountered: