#array #utilities #generics #embedded

no-std array-util

no_std array helpers available without nightly

2 stable releases

1.0.1 Apr 20, 2024
1.0.0 Apr 19, 2024

#78 in No standard library

Download history 252/week @ 2024-04-15 25/week @ 2024-04-22

277 downloads per month

MIT license

56KB
489 lines

array-util

no_std array helpers available without nightly.

Description

Many useful array and slice methods are currently gated by nightly features, though their general functionality and interface is essentially stable. As such this crate provides stable alternatives to the following features, often the same underlying implementation as the current nightly version:

Usage

Users can either import an Ext trait (SliceExt, ArrayExt, or SliceOfArrayExt) traits to bring in the desired methods, or use the bare functions. Note that trait methods have the _ext suffix to avoid collision with the core library methods.

use array_util::ArrayExt;

let a = ["1", "2", "3"];
let b = a.try_map_ext(|v| v.parse::<u32>()).unwrap().map(|v| v + 1);
assert_eq!(b, [2, 3, 4]);

let a = ["1", "2a", "3"];
let b = a.try_map_ext(|v| v.parse::<u32>());
assert!(b.is_err());
let a = ["1", "2", "3"];
let b = array_util::try_map(a, |v| v.parse::<u32>()).unwrap().map(|v| v + 1);
assert_eq!(b, [2, 3, 4]);

let a = ["1", "2a", "3"];
let b = array_util::try_map(a, |v| v.parse::<u32>());
assert!(b.is_err());

Limitations

These functions aren't stabilized because they rely on undecided behaviors. For example, "should compile-time errors be generated for 0 length arrays?" or "What should the associated types and traits of Try be?". As these questions remain unresolved, reliance on the particular answers this crate has chosen in it's implementation may make porting to the eventual stabilized version more painful. If you're just calling functions, you'll probably be fine, but try to avoid using the Ext traits as bounds.

License: MIT

Dependencies

~66KB