-
Notifications
You must be signed in to change notification settings - Fork 17
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
Mandate C++14? #206
Comments
Because I like things that reference things that reference the this pointer (understand who can), I'll just add this message to say 'hell yeah', and link it to #211. |
Merged
Talking to Paul, we're pretty set on requiring C++11, probably after putting out one last C++03 compatible release. C++14 is still debateable. |
And as of #215 we now require C++11. |
And as of #220 we always enable C++11. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GCC 4.8.2 was C++11 feature complete, so any RHEL 7 based system will natively support C++11. GCC 5 was C++14 complete. My experience has been that the supercomputing centers will deploy a GCC installation if requested, so it shouldn't be a problem.
Intel is more dubious. C++11 Status and C++14 Status. Looks like Intel 14+ supports all of the C++11 features we'd want to use and the C++14 auto/decltype feature we'd want.
I think this could be a good move. It would make the code much more readable, I think.
The text was updated successfully, but these errors were encountered: