<execution>, <iosfwd>: Cleanup for operator!= and operator== with reversed order
#3256
Conversation
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
StephanTLavavej
approved these changes
Dec 5, 2022
Member
|
Thanks for finding and improving this! 😸 📈 |
Member
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Member
😻 🧹 ✨ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
These
operator!=andoperator==overloads are being removed in C++20 and later modes in the spirit of P1614R2. Also strengthening the exception specifications for some members and friends offpos, given they don't rely on_Statetype.<experimental/*>,<hash_map>, and<hash_set>are not touched, because they are subject to removal in vNext, and it's unwise for everyone to used these components in C++20 and later modes.It seems that MSVC STL delegates test cases for
fposto libcxx, so I haven't added a test...