Testing change to concept binding #24443
Closed
Conversation
This file contains 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
|
I still think this behavior is weird and the CI failures could be "fixed", but I don't think it's worth it. New style concepts seem to solve my issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This breaks the ability to reference constants defined in concept's body. In order for them to be accessible the type of an operand must get wrapped into the concepts type, as opposed to the generic construct (the concept type here) being formal and a concrete type bound to the operand. I am unaware of anything else that behaves like this and it doesn't seem to make sense to me. I don't think the compiler likes it very much either, but maybe that is a separate problem. Not sure about this one, but I want to run the CI and see what happens.