about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthias Krüger <476013+matthiaskrgr@users.noreply.github.com>2025-03-02 22:44:26 +0100
committerGitHub <noreply@github.com>2025-03-02 22:44:26 +0100
commitc994a293925935164c63dfeb5dd1d7ad2b66b34c (patch)
tree0f502f16c91bea5919d8ba260482a3c76b684a59
parent1762f018f70c164a4c56c147c2d15cbe2fe42873 (diff)
parent596c14ade49d94bd1cfaa26aa34f7ef016f632d6 (diff)
downloadrust-c994a293925935164c63dfeb5dd1d7ad2b66b34c.tar.gz
rust-c994a293925935164c63dfeb5dd1d7ad2b66b34c.zip
Rollup merge of #137871 - pitaj:rangebounds-is_empty-intersect, r=scottmcm
fix `RangeBounds::is_empty` documentation

One-sided ranges are never empty

follow-up for https://github.com/rust-lang/rust/pull/137304#pullrequestreview-2646899461
-rw-r--r--library/core/src/ops/range.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/ops/range.rs b/library/core/src/ops/range.rs
index e0c442e5292..1935268cda8 100644
--- a/library/core/src/ops/range.rs
+++ b/library/core/src/ops/range.rs
@@ -827,7 +827,7 @@ pub trait RangeBounds<T: ?Sized> {
     }
 
     /// Returns `true` if the range contains no items.
-    /// One-sided ranges (`RangeFrom`, etc) always return `true`.
+    /// One-sided ranges (`RangeFrom`, etc) always return `false`.
     ///
     /// # Examples
     ///