Update common_type to C++17 for SFINAE#557
Open
mtnpke wants to merge 1 commit intoelectronicarts:masterfrom
Open
Update common_type to C++17 for SFINAE#557mtnpke wants to merge 1 commit intoelectronicarts:masterfrom
mtnpke wants to merge 1 commit intoelectronicarts:masterfrom
Conversation
Recent C++ standards have made significant changes to common_type, starting with LWG 2408 to make common_type SFINAE-friendly. These changes include the SFINAE-friendliness and add the other changes that C++17 has on top.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recent C++ standards have made significant changes to common_type, starting with LWG 2408 to make common_type SFINAE-friendly. These changes include the SFINAE-friendliness and add the other changes that C++17 has on top.
I initially did this to fix #555, but this is not required once #556 is merged. Nevertheless, I have already written the code, so you can consider it for inclusion.