std::ops::OneSidedRange — Rust trait

What `OneSidedRange` does

OneSidedRange is a trait exposed by the std::ops module of the Rust standard library. It is part of the public, stable API and you can rely on it from any edition of Rust.

As a trait, OneSidedRange defines an interface that other types can implement. Code generic over T: OneSidedRange can call any of its methods on values of any implementing type. The compiler monomorphises generic uses for zero-cost dispatch, while dyn OneSidedRange opts into runtime dispatch with a vtable. The full canonical path is std::ops::OneSidedRange; bring it into scope with use std::ops::OneSidedRange; or refer to it by its full path.

When to use it

Implement OneSidedRange on your own types to plug into the standard library's abstractions, or accept `T: OneSidedRange` as a generic bound on functions that can operate uniformly across every OneSidedRange-shaped type.

Annotated examples

Implementing OneSidedRange for your own type

use std::ops::OneSidedRange;

struct MyType;

// Implementing a std trait is a contract — the compiler enforces every
// required method and associated type. Hover the trait in your editor
// to see the full list of required and provided methods.
impl OneSidedRange for MyType {
    // Required methods go here. Refer to the std::ops::OneSidedRange docs
    // for the exact signatures.
}

Implementing a std trait integrates your type with every generic function and adapter that takes `T: OneSidedRange`. That single impl block can unlock dozens of free helper methods.

For deeper background, see the canonical Rust patterns reference for the broader context behind this section.

Calling generic code that requires OneSidedRange

use std::ops::OneSidedRange;

// `T: OneSidedRange` is a trait bound — only types that implement OneSidedRange
// are accepted. The body can use any of OneSidedRange's methods, and the
// compiler monomorphises the function for each concrete T at the
// call site, so dispatch is always direct.
fn use_with_trait<T: OneSidedRange>(value: T) {
    let _ = value;
}

// Same idea with `impl Trait` for a single argument — equivalent
// when T appears only once in the signature.
fn observe(value: impl OneSidedRange) {
    let _ = value;
}

Trait bounds are the language's zero-cost generics. Each call site is monomorphised, so there is no virtual-dispatch overhead — `dyn OneSidedRange` is a separate, runtime-dispatch flavour you opt into explicitly when you need heterogeneous values.

Common pitfalls

Don't implement OneSidedRange for types that don't naturally satisfy its contract — implementing a trait dishonestly is one of the few ways Rust will compile but produce surprising behaviour at runtime. If you need dynamic dispatch, use `Box<dyn OneSidedRange>` or `&dyn OneSidedRange` instead of a generic parameter.

For deeper background, see an in-depth Rust idioms cheat sheet for the broader context behind this section.

Performance & threading notes

Generic uses (`T: OneSidedRange`) are monomorphised — each concrete T gets its own specialised function, with no virtual-dispatch overhead. `dyn OneSidedRange` adds a single indirection through a vtable, which is fast but blocks some compiler optimisations.

What OneSidedRange does