more_ranges's Introduction

more_ranges

Range types not provided in the standard library.

This crate provides range types that are bounded exclusively below. Specifically, the types provided are:

These ranges operate nearly the same as those in std::ops. However, they do not function as Iterators, nor can they be used in indexing.

Example

The range types provided here can be used by directly specifying their fields:

use more_ranges::{RangeFromExclusive, RangeFromExclusiveToExclusive, RangeFromExclusiveToInclusive};

let range_from_exclusive = RangeFromExclusive { start: 1 };
let range_from_exclusive_to_exclusive = RangeFromExclusiveToExclusive { start: 1, end: 4 };
let range_from_exclusive_to_inclusive = RangeFromExclusiveToInclusive { start: 1, end: 4 };

Minimum Supported Rust Version

This crate is guaranteed to compile on stable rustc 1.28.0 and up.

License

This project is licensed under either of

Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

more_ranges's People

Contributors

Watchers

more_ranges's Issues

All `Index` implementations are not visible in documentation.

All of the Index and IndexMut implementations are not visible in docs generated on nightly.

This is a known issue, and it looks like a solution is in the works. 0.2.0's release will be blocked until this is fixed, as I don't want incomplete docs to be published.

0.2.0 Checklist

This is the checklist of things that need to happen before the 0.2.0 release.

Support Iterating and Indexing on Nightly

It seems that supporting Iterating and Indexing on stable is tricky at the moment, due std::iter::Step and std::slice::SliceIndex having experimental APIs. For Step, I've considered using the step crate to accomplish the same purpose. The only issue is it forces users to implement step::Step if they want to iterate over a custom steppable range.

An alternative is to make iterating and indexing both available, in the same manner as they are implemented for the standard library range types, on nightly channels only. It seems that [autocfg](https://crates.io/crates/autocfg does not currently offer probing channels yet, although it may come in the future. rustc_version is another crate which can probe channels.

Another possibility is to lock iterating and indexing behind a nightly feature, allowing users to opt-in using cargo features.

Recommend Projects