6 releases (3 stable)

1.1.1 Jun 30, 2023
1.1.0 Jan 13, 2021
1.0.0 Apr 25, 2020
0.99.0 Apr 11, 2020
0.99.0-dev.3 Mar 26, 2020

#51 in Text processing

Download history 34030/week @ 2024-01-03 36239/week @ 2024-01-10 39028/week @ 2024-01-17 39701/week @ 2024-01-24 42937/week @ 2024-01-31 46525/week @ 2024-02-07 48310/week @ 2024-02-14 45544/week @ 2024-02-21 48618/week @ 2024-02-28 51594/week @ 2024-03-06 51497/week @ 2024-03-13 53948/week @ 2024-03-20 49635/week @ 2024-03-27 47127/week @ 2024-04-03 45416/week @ 2024-04-10 37908/week @ 2024-04-17

189,401 downloads per month
Used in 244 crates (28 directly)


430 lines


Build Status Crates.io API reference

A library that provides newtype wrappers for u32 and (u32, u32) for use as text offsets.

See the docs for more.


Licensed under either of

at your option.


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.


Newtypes for working with text sizes/ranges in a more type-safe manner.

This library can help with two things:

  • Reducing storage requirements for offsets and ranges, under the assumption that 32 bits is enough.
  • Providing standard vocabulary types for applications where text ranges are pervasive.

However, you should not use this library simply because you work with strings. In the overwhelming majority of cases, using usize and std::ops::Range<usize> is better. In particular, if you are publishing a library, using only std types in the interface would make it more interoperable. Similarly, if you are writing something like a lexer, which produces, but does not store text ranges, then sticking to usize would be better.

Minimal Supported Rust Version: latest stable.