1 unstable release

0.1.0 May 15, 2023

#315 in Embedded development

Download history 3317/week @ 2024-03-14 3348/week @ 2024-03-21 1983/week @ 2024-03-28 2065/week @ 2024-04-04 1882/week @ 2024-04-11 1994/week @ 2024-04-18 2035/week @ 2024-04-25 1991/week @ 2024-05-02 1841/week @ 2024-05-09 2239/week @ 2024-05-16 1660/week @ 2024-05-23 2481/week @ 2024-05-30 1422/week @ 2024-06-06 1679/week @ 2024-06-13 1510/week @ 2024-06-20 1139/week @ 2024-06-27

5,983 downloads per month
Used in 9 crates (2 directly)



[2]: https://github.com/Robbepop/intx/actions/workflows/rust.yml [4]: https://docs.rs/intx [6]: https://crates.io/crates/intx

Continuous Integration Documentation Crates.io
[ci][2] [docs][4] [crates][6]

intx - Non-standard fixed bitwidth integers for Rust

WARNING: This crate is not yet production ready as it is missing lots of tests.

This crate provides new integer types with non-standard and fixed bitwidths such as U24, I48, U96 and so forth with a focus on data layout and alignment.

  • All integers provided by this crate require the minimum number of bytes for their representation. For example, U24 requires 3 bytes, I48 requires 6 bytes.
  • The alignment of all integer types provided by this crate is always 1. If another alignment is required it is recommended to wrap the integer type in a newtype and enforce an alignment via #[align(N)].
  • As of now the provided integers do not have a rich set of arithmetic methods defined on them. It is instead expected to convert them to Rust primitive integers, apply the computation and eventually convert the result back. This might be supported in the future if requested.
  • The binary representation of integer types provided by this crate is in twos-complement just like Rust's built-in integer types.

Data Layout

All integer types provided by this crate internally consists of a single byte array. For example, the structure of U24 is struct U24([u8; 3]); allowing for optimal memory usage and an alignment of 1 (if needed).


Integer types provided by this crate only have very a minimal API surface.

  • Traits implemented by all of the integer types are the following:

    • Clone, Copy, Default, Eq, PartialEq, Ord, PartialOrd, Hash
      • Common traits are all implemented as efficiently as possible for every integer type.
    • Debug, Display, Binary, Octal, LowerHex, UpperHex, LowerExp, UpperExp
      • Integer types mimick the display representation of the next larger Rust built-in integer type.
  • Endian-aware conversion routines are also implemented:

    • from_ne_bytes, to_ne_bytes: Convert from and to native-endian bytes. (always efficient)
    • from_le_bytes, to_le_bytes: Convert from and to little-endian bytes.
    • from_be_bytes, to_be_bytes: Convert from and to big-endian bytes.
  • Rich From and TryFrom implementations:

    • All provided integer types have a very rich set of From and TryFrom trait implementations to efficiently convert between different integer types and Rust built-in integers.


The focus of this crate is data layout, alignment and space-optization. It was crafted as an experiment when the wasmi interpreter required a more memory efficient representation of its internal bytecode. For example using a 3 bytes sized U24 instead of a 4 byte sized u32 in certain places allows the Rust compiler to pack data structures more efficiently in some cases, especially when using enum types.

If your primary focus is on the logical side where you are mostly interested in arithmetic operations on integer types with non-standard but fixed bitwidths then maybe the ux crate is a better fit for you.


The alternative ux crate provides non-standard and fixed bitwidth integers as well but the focus of both crates is very different.

Property intx ux
size_of All integer types require the minimum number of bytes for their representation. For example, size_of<intx::U24>() == 3 All integer types have the same size_of as the next biggest Rust built-in integer primitive. For example, size_of<ux::u24>() == size_of<u32>() == 4
align_of All integer types have an alignment of 1. If another alignment is needed it is possible to wrap the integer type in a newtype and enforce another alignment via #[align(N)] All integer types have the same align_of as the next biggest Rust built-in integer primitive. For example align_of<ux::u24>() == align_of<u32> == 4.
Focus Data layout and alignment of packed data structures using integers. Arithmetic operations on non-standard bitwidth integer types.
API Integer types provide a minimal API surface. Mostly From and TryFrom impls between integers and Rust primitives as well as endian-aware byte conversions known from Rust primitives such as to_ne_bytes and from_le_bytes. Integer types try to mimick Rust built-in integer types providing a fair amount of arithmetic operations on them.

Both crates provide rich support for conversions between different integer types and Rust primitives.


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.

No runtime deps