Tracking Issue for range_bounds_is_empty (original) (raw)
Navigation Menu
Appearance settings
- AI CODE CREATION
* GitHub CopilotWrite better code with AI
* GitHub SparkBuild and deploy intelligent apps
* GitHub ModelsManage and compare prompts
* MCP RegistryNewIntegrate external tools - DEVELOPER WORKFLOWS
* ActionsAutomate any workflow
* CodespacesInstant dev environments
* IssuesPlan and track work
* Code ReviewManage code changes - APPLICATION SECURITY
* GitHub Advanced SecurityFind and fix vulnerabilities
* Code securitySecure your code as you build
* Secret protectionStop leaks before they start - EXPLORE
* Why GitHub
* Documentation
* Blog
* Changelog
* Marketplace
- AI CODE CREATION
- BY COMPANY SIZE
* Enterprises
* Small and medium teams
* Startups
* Nonprofits - BY USE CASE
* App Modernization
* DevSecOps
* DevOps
* CI/CD
* View all use cases - BY INDUSTRY
* Healthcare
* Financial services
* Manufacturing
* Government
* View all industries
- BY COMPANY SIZE
- EXPLORE BY TOPIC
* AI
* Software Development
* DevOps
* Security
* View all topics - EXPLORE BY TYPE
* Customer stories
* Events & webinars
* Ebooks & reports
* Business insights
* GitHub Skills - SUPPORT & SERVICES
* Documentation
* Customer support
* Community forum
* Trust center
* Partners
- EXPLORE BY TOPIC
- COMMUNITY
* GitHub SponsorsFund open source developers - PROGRAMS
* Security Lab
* Maintainer Community
* Accelerator
* Archive Program - REPOSITORIES
* Topics
* Trending
* Collections
- COMMUNITY
- Pricing
Provide feedback
We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Saved searches
Use saved searches to filter your results more quickly
Appearance settings
Notifications You must be signed in to change notification settings
Additional navigation options
Open
Open
Tracking Issue for range_bounds_is_empty
#137300
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-design-concernsStatus: There are blocking design concerns.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.
Description
opened
Feature gate: #![feature(range_bounds_is_empty)]
This is a tracking issue for the is_empty method on RangeBounds.
Public API
// core::ops pub trait RangeBounds<T: ?Sized> { ...
fn is_empty(&self) -> bool
where
T: PartialOrd,
{
...
}}
Steps / History
- ACP: IntoBounds::clamp and RangeBounds::is_empty libs-team#539
- Implementation: add IntoBounds::intersect and RangeBounds::is_empty #137304
- Final comment period (FCP)1
- Stabilization PR
Unresolved Questions
(Excluded(1), Excluded(2))is considered to be non-empty. This could be a foot gun. Should we add a trait bound to avoid it? Related issues:
Footnotes
Metadata
Metadata
Assignees
No one assigned
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-design-concernsStatus: There are blocking design concerns.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.
Type
No type
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests