-
Notifications
You must be signed in to change notification settings - Fork 20
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
Adding optional usage of C++ 17 #67
Conversation
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, should we add a CI build that tests C++17 build? Otherwise we'll break it. Also perhaps add a GCC one for the previous PR?
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
I've added them in, and am seeing some build errors for macos-latest + CXX17. Would you be able to take a look? |
Should be fixed in upstream snmalloc: |
This PR makes a small set of changes which enable the library to be built in C++ 17 with extremely strict flags. No functionality is affected and the C++ 17 path is entirely optional.