-
Notifications
You must be signed in to change notification settings - Fork 14.4k
[libc++] P3379R1: Constrain std::expected
equality operators
#117664
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
002fcac
[libc++] P3379R1: Constrain 'std::expected' equality operators
xiaoyang-sde 408b331
[libc++] P3379R1: Constrain 'std::expected' equality operators
xiaoyang-sde 6d540b6
[libc++] P3379R1: Constrain 'std::expected' equality operators
xiaoyang-sde 02d1d91
[libc++] P3379R1: Constrain 'std::expected' equality operators
xiaoyang-sde 805ac6a
[libc++] P3379R1: Constrain 'std::expected' equality operators
xiaoyang-sde 437dec5
[libc++] P3379R1: Constrain 'std::expected' equality operators
xiaoyang-sde 307559f
[libc++] P3379R1: Constrain 'std::expected' equality operators
xiaoyang-sde File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
The
convertible_to
concept is stricter than the plain "(implicitly) convertible to". The latter can be expressed by__is_core_convertible
in<__type_traits/is_core_convertible.h>
.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.
I guess we can have the following.
Internal concept
__core_convertible_to
in the<__concepts/core_convertible_to.h>
internal headerThere 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.
Thank you for writing this! I'll take a look.
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.
Would you like to draft a patch for this header if you have time? I can rebase and use your header. This will ensure that you receive credit for your work! Otherwise, I can include it in this patch myself.
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.
It seems we used
__boolean_testable
to implement the constraints foroperator==
instd::reference_wrapper
. (https://github.com/llvm/llvm-project/blob/main/libcxx/include/__functional/reference_wrapper.h#L75-L81)Should we consider making them consistent?