Skip to content
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

Add Range::is_empty() and Range::bounds() #188

Closed
wants to merge 1 commit into from

Conversation

konstin
Copy link
Member

@konstin konstin commented Mar 11, 2024

@konstin konstin force-pushed the konsti/range-bounds branch from 71a7ce8 to be6883f Compare March 11, 2024 20:36
@Eh2406
Copy link
Member

Eh2406 commented Mar 11, 2024

Range::bounds can be built on Range::iter, and it seems like a somewhat niche use case.

Range::is_empty is == Range::empty(), but might be clearer.

konstin added a commit to astral-sh/uv that referenced this pull request Mar 11, 2024
I'm trying to reduce our pubgrub upstream divergences and since we only have one usage of our custom `Range::bounds` it seems more reasonable to do this in uv directly than in pubgrub (pubgrub-rs/pubgrub#188 (comment)).
@konstin
Copy link
Member Author

konstin commented Mar 11, 2024

Good point, i've split off Range::is_empty() (#189) and removed our Range::bounds() usage (astral-sh/uv#2363)

Closing in favor of #189

@konstin konstin closed this Mar 11, 2024
konstin added a commit to astral-sh/uv that referenced this pull request Mar 11, 2024
I'm trying to reduce our pubgrub upstream divergences and since we only
have one usage of our custom `Range::bounds` it seems more reasonable to
do this in uv directly than in pubgrub
(pubgrub-rs/pubgrub#188 (comment)).
@konstin konstin deleted the konsti/range-bounds branch March 13, 2024 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants