Conversation
Member
|
Being restrictive sounds OK for now. Why does |
nalimilan
reviewed
Sep 14, 2021
Member
Author
Ah - you are right. |
Member
Author
|
Ah - I was right originally so it is a |
nalimilan
reviewed
Sep 20, 2021
Co-authored-by: Milan Bouchet-Valat <nalimilan@club.fr>
bkamins
commented
Sep 20, 2021
bkamins
commented
Sep 20, 2021
bkamins
commented
Sep 20, 2021
Member
Author
|
@nalimilan - this should be good to have a look at again. |
nalimilan
approved these changes
Sep 20, 2021
Member
Author
|
Thank you! |
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
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.
Fixes #2875
I was thinking that we might make it even more flexible and allow predicate to be mixed with other selectors in
Cols, but for now I proposed a restrictive version. @nalimilan - do you think we should be more flexible?