#cast #conversion #convert #no-alloc #from #into #no-std

no-std cove

Casts Of Varying Elegance (COVE): extension traits for casting numerical types

2 releases (1 stable)

1.0.0 Jun 24, 2024
0.8.0 Jun 24, 2024
0.7.0 Jun 13, 2024
0.4.0 Jan 15, 2024
0.3.0 Sep 13, 2023

#460 in Rust patterns

MIT license

135KB
1K SLoC

cove

Casts Of Varying Elegance

Crates.io MIT licensed Build Status Maintenace

Provides a collection of extension traits to improve the safety and maintainability of numerical casts. Cove's primary goals are:

  • Clarity: the programmer's intention for a cast is clear from the name
  • Correctness: suspicious casts via as can be reduced or eliminated altogether
  • Performance: in release builds, cove's casts generally compile down to the same assembly as manual implementations
  • Independence: no required dependencies and the only optional dependency is std

Quick Usage

use cove::prelude::*;
use core::num::{NonZeroI8, NonZeroI32, NonZeroI64, NonZeroU16, NonZeroU64};

// Check whether a cast is lossy at runtime
assert_eq!(8i16.cast::<u8>()?, 8u8);
assert!(0u128.cast::<NonZeroI8>().is_err());

// Of course, turbofish disambiguation is unnecessary if the compiler can deduce the type:
fn foo(x: u8) -> u8 {x}
assert_eq!(foo(2i16.cast()?), 2u8);

// If the cast ends up being lossy, you can usually still use the lossy value if you like:
assert_eq!(9.2f64.cast::<usize>().unwrap_err().to, 9usize);

// ...or more concisely:
assert_eq!(9.2f64.cast::<usize>().lossy(), 9usize);

// Perhaps you don't mind if the cast is lossy, but you'd like to get as close as possible:
assert_eq!(300u32.cast::<u8>().closest(), 255u8);
assert_eq!((-7isize).cast::<u16>().closest(), 0u16);
assert_eq!(-4.6f32.cast::<i16>().closest(), -5i16);
assert_eq!(-0.0f64.cast::<NonZeroI32>().closest(), NonZeroI32::new(-1).unwrap());

// If you are supremely confident a cast is lossless you can always use unwrap_unchecked:
assert_eq!(unsafe {90u32.cast::<u8>().unwrap_unchecked()}, 90);

// ...but if the unsafeness makes you uncomfortable you might prefer cove's assumed_lossless,
// which will use a debug_assert instead of unsafe (and just risk lossiness in release builds):
assert_eq!(90u32.cast::<u8>().assumed_lossless(), 90);

// If desired, you can instead preserve bits (rather than mathematical value) across a cast:
assert_eq!(NonZeroI64::new(-1).unwrap().cast::<u64>().bitwise(), u64::MAX);
assert_eq!(10f32.cast::<u32>().bitwise(), 1_092_616_192u32);

// If the types guarantee a lossless cast, you can of course always use `From`/`Into`:
assert_eq!(NonZeroU64::from(NonZeroU16::new(12).unwrap()), NonZeroU64::new(12).unwrap());

// ...but what if those traits aren't provided because the cast could be lossy on some other
// platform? If you don't mind losing portability, try out cove's `lossless`. This will only
// compile on platforms where usize is at least 64 bits:
assert_eq!(31u64.cast::<usize>().lossless(), 31usize);

Features

Cove supports one feature, std, which is included in the default features. Enabling this feature (or rather, failing to disable it) enables support for the Rust standard library. If this is disabled, cove depends only on the Rust core library. Enabling std causes cove's error types to implement std::error::Error; otherwise they do not, as at the time of writing core::error::Error is unstable. In addition, some cast implementations are controlled by this feature, as the rust standard library allows for optimizations via intrinsics not available in stable core.

  • Read about how to use cove's casts
  • Read about generic bounds for cove's casts
  • Read about extending cove's casts to new types
  • Read about the motivation behind cove
  • Read about performance considerations when using cove
  • Read about testing considerations with cove

No runtime deps

Features