Skip to content

[libc++][ranges] Implement ranges::contains_subrange #66963

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

Merged
merged 36 commits into from
Feb 13, 2024

Conversation

ZijunZhaoCCK
Copy link
Contributor

No description provided.

@llvmbot llvmbot added the libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi. label Sep 21, 2023
@ZijunZhaoCCK ZijunZhaoCCK marked this pull request as ready for review September 21, 2023 21:21
@ZijunZhaoCCK ZijunZhaoCCK requested a review from a team as a code owner September 21, 2023 21:21
@ZijunZhaoCCK ZijunZhaoCCK self-assigned this Sep 21, 2023
Copy link
Member

@huixie90 huixie90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for contributing! I have not looked at the tests yet. Please let me know if my comments on the header file is unclear. Thank you!

@github-actions
Copy link

github-actions bot commented Sep 27, 2023

✅ With the latest revision this PR passed the C/C++ code formatter.

@ZijunZhaoCCK ZijunZhaoCCK marked this pull request as draft October 2, 2023 05:42
@shafik
Copy link
Collaborator

shafik commented Oct 2, 2023

Please make sure you add a description to your PR. This is what usually goes into the git log and we want those entries to be as descriptive and helpful for folks who read the git logs, thank you.

@philnik777
Copy link
Contributor

Please make sure you add a description to your PR. This is what usually goes into the git log and we want those entries to be as descriptive and helpful for folks who read the git logs, thank you.

Do you have any specific suggestions what should be in the message? The libc++ "I implement something" patches are most of the time quite straight-forward, since you can look at the standard and know what's going on. It's also the best source, since it's the authoritative document here, and is also what anybody who cares to actually look at the patch should check against for correctness.

@philnik777 philnik777 added the ranges Issues related to `<ranges>` label Oct 6, 2023
@var-const
Copy link
Member

Please make sure you add a description to your PR. This is what usually goes into the git log and we want those entries to be as descriptive and helpful for folks who read the git logs, thank you.

Do you have any specific suggestions what should be in the message? The libc++ "I implement something" patches are most of the time quite straight-forward, since you can look at the standard and know what's going on. It's also the best source, since it's the authoritative document here, and is also what anybody who cares to actually look at the patch should check against for correctness.

+1 -- I'm in favor of descriptive commit messages in general, but in this case I'm not sure what would be useful to add beyond "Implement ranges::contains_subrange".

@var-const var-const changed the title [libc++] Implement ranges::contains_subrange [libc++][ranges] Implement ranges::contains_subrange Oct 13, 2023
Copy link
Member

@var-const var-const left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the patch!

@ldionne
Copy link
Member

ldionne commented Nov 16, 2023

Gentle ping. There's outstanding feedback to address on this review. @ZijunZhaoCCK if you don't think you'll have time to pursue this PR anymore, it's all good but please let us know so we can assign it to someone else!

@ZijunZhaoCCK
Copy link
Contributor Author

Gentle ping. There's outstanding feedback to address on this review. @ZijunZhaoCCK if you don't think you'll have time to pursue this PR anymore, it's all good but please let us know so we can assign it to someone else!

Sorry for the late reply! I can’t make it a priority right now, but I’ll definitely do it when things calm down, maybe in January. If someone want to do it right now, I can stop pursuing this PR.

@var-const var-const assigned var-const and unassigned huixie90 and ZijunZhaoCCK Dec 13, 2023
Copy link
Member

@mordante mordante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your patch!
I mainly glossed over the patch, and left some comments.

@ZijunZhaoCCK ZijunZhaoCCK force-pushed the libcxx-ranges-contains-subrange branch from f713b60 to 67c2e35 Compare January 2, 2024 22:41
@H-G-Hristov
Copy link
Contributor

Just a gentle reminder. You should probably also update the release notes, the status page and the feature test macro: #define __cpp_lib_ranges_contains 20XXXXL // also in <algorithm>

ZijunZhaoCCK and others added 15 commits January 8, 2024 18:15
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
5. add ranges::contains_subrange() in module.modulemap.in
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
5. add ranges::contains_subrange() in module.modulemap.in
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
5. add ranges::contains_subrange() in module.modulemap.in
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
5. add ranges::contains_subrange() in module.modulemap.in
@ldionne ldionne marked this pull request as ready for review January 10, 2024 19:12
Copy link
Member

@var-const var-const left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks a lot for pushing this through and addressing all the feedback!

@var-const
Copy link
Member

Looks like the CI failure was fixed by #77672 -- merging main should resolve this.

ZijunZhaoCCK and others added 7 commits February 12, 2024 22:22
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
5. add ranges::contains_subrange() in module.modulemap.in
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
5. add ranges::contains_subrange() in module.modulemap.in
2. add several test cases: like when both range and subrange are empty
3. reformat
4. nit to fix
5. add ranges::contains_subrange() in module.modulemap.in
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi. ranges Issues related to `<ranges>`
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants