Different `impl RangeBounds` for `RangeInclusive<&T>` and `RangeInclusive`

⚓ Rust 📅 2025-10-08 👤 surdeus 👁️ 10

Warning

This post was published 103 days ago. The information described in this article may have changed.

Info

This post is auto-generated from RSS feed The Rust Programming Language Forum - Latest topics. Source: Different `impl RangeBounds` for `RangeInclusive<&T>` and `RangeInclusive`

Their end_bound are different. Shouldn't they work the same way?

github.com/rust-lang/rust

library/core/src/ops/range.rs

5767910cb


      
          impl<T> RangeBounds<T> for RangeInclusive<T> {
              fn start_bound(&self) -> Bound<&T> {
                  Included(&self.start)
              }
              fn end_bound(&self) -> Bound<&T> {
                  if self.exhausted {
                      // When the iterator is exhausted, we usually have start == end,
                      // but we want the range to appear empty, containing nothing.
                      Excluded(&self.end)
                  } else {
                      Included(&self.end)
                  }
              }
          }

github.com/rust-lang/rust

library/core/src/ops/range.rs

5767910cb


      
          impl<T> RangeBounds<T> for RangeInclusive<&T> {
              fn start_bound(&self) -> Bound<&T> {
                  Included(self.start)
              }
              fn end_bound(&self) -> Bound<&T> {
                  Included(self.end)
              }
          }

2 posts - 2 participants

Read full topic

🏷️ Rust_feed

👍 󠁮󠁮󠁮󠁮 👎 󠁮󠁮󠁮󠁮