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)¹
• 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:
  • RangeBounds::is_empty has a nonsensical implementation #149625
  • [ACP] RangeBounds::overlaps libs-team#277 (comment)
  • IntoBounds::clamp and RangeBounds::is_empty libs-team#539