Implement LWG-3886 Monad mo' problems (in optional and expected)
#5232
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
Also speculatively implement LWG-3424 for `expected`.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
StephanTLavavej
approved these changes
Jan 13, 2025
|
Thanks! 😻 I noticed that LWG-3424 wasn't completely implemented for |
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
📈 💚 😻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Also speculatively implement LWG-3424 for
expectedto avoidvolatile-qualified return types, and complete the speculative implementation foroptional.Some parts of the resolution is not meaningful yet and not tested due to LWG-3891.
Fixes #5119.