Expand description
§orx-v
Traits to unify all vectors!
The focus of this crate is mainly computation and algorithms. The goal is to allow for a generic algorithm implementation that can be called by many polymorphic vector types having a corresponding practical use case.
You may find an article discussing the motivation here and various examples in the examples folder of the repository.
§Traits
Two vector traits are defined: one for immutable vectors and the other one extending it to mutable vectors.
§Immutable Vectors: NVec<D, T>
NVec<D, T> is a D
dimensional vector where the scalar elements are of type T
.
At its core, the following define the vectors’ shared behavior:
at
: efficient random access by indicescard
: complete knowledge of its sizeall
: efficient serial access over all scalar elements
§Random Access
The first shared functionality is defined by the at
method. It is analogous to the index operator of a Vec, however, extended to higher dimensions.
fn at(&self, idx: impl IntoIdx<D>) -> T;
Below are some examples for D1
and D2
vectors.
use orx_v::*;
let v1 = vec![1, 7, 42];
assert_eq!(v1.at(2), 42);
let v1 = V.d1().constant(42);
assert_eq!(v1.at(121), 42);
let v1 = V.d1().fun(|[i]| 2 * i + 7);
assert_eq!(v1.at(10), 27);
let v2 = vec![vec![1, 2], vec![3, 4, 5]];
assert_eq!(v2.at([0, 1]), 2);
assert_eq!(v2.at([1, 2]), 5);
let mut v2 = V.d2().sparse(1000);
v2.set([2, 1], 21);
assert_eq!(v2.at([0, 1]), 1000);
assert_eq!(v2.at([2, 1]), 21);
assert_eq!(v2.at([1, 0]), 1000);
As the examples reveal, various useful concrete types already implement the vector traits, such as:
- the standard vector, arrays, slices;
- ndarray arrays such as Array1, Array2, etc.;
- sparse vectors;
- caching or memoizing vectors;
- functional vectors, and so on.
Further, due to the abstraction through traits, we can have composed definitions. For instance
Vec<T>
andSparseVec<D1, T>
both implementNVec<D1, T>
.- Then,
Vec<Vec<T>>
andVec<SparseVec<D1, T>>
both implementNVec<D2, T>
. - Actually, any
Vec<V>
whereV: NVec<D1, T>
automatically implementsNVec<D2, T>
.
§Cardinality
The second shared functionality is the knowledge of the vector’s and all of its children’s cardinality, all the way down to scalars. This is provided by the card
method. It is analogous to len
method of common collections; however, extended to provide complete cardinality information rather than only the number of immediate children.
fn card(&self, idx: impl Into<D::CardIdx>) -> usize;
Below, you may see examples for D1
vectors. Notice that some vectors are naturally unbounded, such as a constant vector, a functional vector or a sparse vector. The examples also illustrate how to define their bounds whenever needed.
use orx_v::*;
let v1 = vec![2, 3, 4];
assert_eq!(v1.card([]), 3);
// unbounded vectors
let sparse_elements: DefaultLookup<D1, _> = [([1], 42), ([7], 12)].into_iter().collect();
let v1 = V.d1().sparse_from(sparse_elements, 0);
assert_eq!(v1.at(7), 12);
assert_eq!(v1.at(123456), 0); // never out of bounds
assert_eq!(v1.card([]), usize::MAX);
assert!(!v1.is_bounded());
// add bound to unbounded vectors
let v1 = v1.bounded(10);
assert_eq!(v1.card([]), 10);
assert!(v1.is_bounded());
assert_eq!(v1.try_at(123456), None);
The following D2
examples illustrate how card
method can be used for all lower dimensions.
use orx_v::*;
let v2 = vec![
vec![1, 2],
vec![],
vec![3, 4, 5],
];
assert_eq!(v2.card([]), 3);
assert_eq!(v2.card([1]), 0);
assert_eq!(v2.card([2]), 3);
// this is equivalent to
assert_eq!(v2.child(2).card([]), 3);
// unbounded vectors
let v2 = V.d2().fun(|[i, j]| 2 * i + j);
assert_eq!(v2.card([]), usize::MAX);
assert!(!v2.is_bounded());
assert_eq!(v2.card([100]), usize::MAX);
assert!(!v2.child(100).is_bounded());
// add rectangular bounds as in matrices
let v2 = V
.d2()
.fun(|[i, j]| 2 * i + j)
.with_rectangular_bounds([2, 3]);
assert_eq!(v2.card([]), 2);
assert_eq!(v2.card([0]), 3);
assert_eq!(v2.card([1]), 3);
// add variable bounds as in jagged arrays
let num_elements = vec![2, 0, 3]; // any NVec<D1, usize>
let v2 = V
.d2()
.fun(|[i, j]| 2 * i + j)
.with_variable_bounds(&num_elements);
assert_eq!(v2.card([]), 3);
assert_eq!(v2.card([0]), 2);
assert_eq!(v2.card([1]), 0);
assert_eq!(v2.card([2]), 3);
The num_elements
definition also demonstrates the benefit of abstraction. In this example, we used a Vec, but we could’ve used any NVec<D1, usize>
implementation. For instance, assume we have a D2
vector where each row has 1000 elements while the last element has 1. We can easily represent this with a functional vector or a sparse vector and avoid allocating the entire vector of number of elements.
§Sequential Access
Not to be confused with iter()
method on collections, all
method yields the inner-most scalar elements.
In order to iterate over the immediate children, children
method can be used instead.
use orx_v::*;
let vec = vec![vec![0, 1], vec![], vec![2]]; // V2
// inner-most elements, scalars
let mut all = vec.all();
assert_eq!(all.next(), Some(0));
assert_eq!(all.next(), Some(1));
assert_eq!(all.next(), Some(2));
assert_eq!(all.next(), None);
// immediate children belonging to previous dimension (D1 here)
let mut children = vec.children();
assert_eq!(children.next().unwrap().equality(&[0, 1]), Equality::Equal);
assert_eq!(children.next().unwrap().equality(&[]), Equality::Equal);
assert_eq!(children.next().unwrap().equality(&[2]), Equality::Equal);
assert!(children.next().is_none());
§Mutable Vectors: NVecMut<D, T>
As expected, NVecMut extends NVec
; i.e., NVecMut<D, T>: NVec<D, T>
.
Its core functionality is defined by the at_mut
method.
fn at_mut<Idx: IntoIdx<D>>(&mut self, idx: Idx) -> &mut T;
use orx_v::*;
let mut v1 = vec![1, 7, 42];
*v1.at_mut(1) = 7;
v1.set(2, 21); // if you prefer
let mut v2 = vec![vec![1, 2], vec![3, 4, 5]];
*v2.at_mut([0, 1]) = 21;
v2.set([1, 2], 7);
let mut v2 = V.d2().sparse(1000);
*v2.at_mut([1, 2]) = 12;
v2.set([2, 1], 21);
§Trait Aliases
The following trait aliases can be used instead, to fix the first generic type parameter on dimension.
V1<T> <====> NVec<D1, T>
V1Mut<T> <====> NVecMut<D1, T>
V2<T> <====> NVec<D2, T>
V2Mut<T> <====> NVecMut<D2, T>
...
§V for Vectors!
V is basically the entry point of builders for various vector types of multi dimensional vectors. It is followed by the dimension of the vector to be created, such as V.d1()
or V.d3()
. Next we can call methods to create special vectors such as:
- ConstantVec
V.d1().const(42)
- a vector that yields only 42 for all indices
- EmptyVec
V.d3().empty::<i32>()
- a vector with no elements, zero cardinality
- SparseVec
V.d2().sparse(1000)
- a sparse vector where all elements which are not explicitly set are equal to 1000
- FunVec
V.d2().fun(|[i, j]| euclidean(&locations[i], &locations[j]))
- a lazy vector which computes elements on the fly as requested
- CachedVec
V.d2().fun(|[i, j]| euclidean(&locations[i], &locations[j])).into_cached()
- also a lazy vector vector; however, it caches or memoizes computed elements
§Practical Example
To demonstrate when and why these traits might be useful, let’s assume that we are implementing the two-opt which is a local search algorithm to solve the traveling salesperson problem. The algorithm takes a tour and keeps modifying it until its distance can no longer be reduced within the two-opt neighborhood. We can have our generic implementation as follows.
use orx_v::*;
fn apply_two_opt(mut tour: impl V1Mut<usize>, i: usize, j: usize) {
let mut i = i + 1;
let mut j = j;
while i < j {
let t = tour.at(i);
*tour.at_mut(i) = tour.at(j);
*tour.at_mut(j) = t;
i += 1;
j -= 1;
}
}
fn two_opt(distances: impl V2<u32>, mut tour: impl V1Mut<usize>) -> u32 {
let mut improvement = 0;
let d = distances;
let n = tour.card([]);
let mut improved = true;
while improved {
improved = false;
for i in 0..(n - 1) {
let i1 = tour.at(i);
let i2 = tour.at(i + 1);
for j in (i + 2)..n {
let j1 = tour.at(j);
let j2 = tour.at((j + 1) % n);
let removed_len = d.at([i1, i2]) + d.at([j1, j2]);
let added_len = d.at([i1, j1]) + d.at([i2, j2]);
if removed_len > added_len {
improved = true;
improvement += removed_len - added_len;
apply_two_opt(&mut tour, i, j);
}
}
}
}
improvement
}
This implementation is not much different than the implementation where we would use Vec<usize>
for a tour and Vec<Vec<u32>>
for a distance matrix.
However, it is much different in the caller side.
We can call this algorithm with a wide range of input types that make sense in different situations.
let n = 100;
let mut tour: Vec<_> = initial_tour(n);
// complete matrix stored as a V2
{
// Vec<Vec<u32>>
let distances: Vec<Vec<u32>> = complete_distance_matrix_d2(n);
let _improvement = two_opt(&distances, &mut tour);
// ndarray::Array2
let distances: Array2<u32> = complete_ndarray_d2(n);
let _improvement = two_opt(&distances, &mut tour);
}
// complete matrix stored as a flattened V1
{
// Vec<u32> as flattened matrix
let distances: Vec<u32> = complete_distance_matrix_d1(n);
let _improvement = two_opt(distances.as_jagged_with_uniform_lengths(n), &mut tour);
// ndarray::Array1 as flattened matrix
let distances: Array1<u32> = complete_ndarray_d1(n);
let _improvement = two_opt(distances.as_jagged_with_uniform_lengths(n), &mut tour);
}
// sparse matrix
let finite_distances: HashMap<[usize; 2], u32> = finite_distances_map(n);
let distances = V.d2().sparse_from(finite_distances, 10000);
let _improvement = two_opt(&distances, &mut tour);
// functional matrix
let locations: Vec<Location> = get_locations(n);
let distances = V
.d2()
.fun(|[i, j]| euclidean_distance(&locations[i], &locations[j]));
let _improvement = two_opt(&distances, &mut tour);
// functional matrix: ignore from-to depot (node 0) links
let locations: Vec<Location> = get_locations(n);
let distances = V.d2().fun(|[i, j]| match (i, j) {
(0, _) => 0,
(_, 0) => 0,
_ => euclidean_distance(&locations[i], &locations[j]),
});
let _improvement = two_opt(&distances, &mut tour);
// cached matrix
let locations: Vec<Location> = get_locations(n);
let distances = V
.d2()
.fun(|[i, j]| routing_engine(&locations[i], &locations[j]))
.into_cached();
let _improvement = two_opt(&distances, &mut tour);
// uniform distances
let distances = V.d2().constant(10);
let _improvement = two_opt(&distances, &mut tour);
§Matrices
In addition to vector traits, specialized Matrix<T> and MatrixMut<T> traits are also defined to allow for polymorphic matrix types.
Their interface is naturally very similar to those of V2<T>
and V2Mut<T>
except that they require rectangular bounds.
Any V2
vector with rectangular cardinality can be converted into or viewed as a row-major or column-major matrix by calling into_matrix
or as_matrix
methods of the V2AsMatrix trait.
Further, any V1
vector can be transformed or viewed as a flattened matrix by calling v1_into_matrix
or v1_as_matrix
methods of the V1AsMatrix trait.
§Features
Vector trait implementations for vectors in well known external libraries are being included in this crate via features. For instance, you may add “ndarray” feature to be able to use “ndarray::Vector1” as a “V1”, or “Vector2” as a “V2”, etc.
std is enabled as the default feature, please set “default-features=false” when working in no-std programs.
§Contributing
Contributions, ideas and feedback are welcome!
If you notice an error, have a question or think something could be improved, or think certain data types must also implement the vector traits, please open an issue or create a PR.
§License
This library is licensed under MIT license. See LICENSE for details.
Re-exports§
pub use matrices::Matrix;
pub use matrices::MatrixColMajor;
pub use matrices::MatrixColMajorMut;
pub use matrices::MatrixMut;
pub use matrices::MatrixRowMajor;
pub use matrices::MatrixRowMajorMut;
pub use matrices::V1AsMatrix;
pub use matrices::V2AsMatrix;
Modules§
- Matrix representations.
Macros§
- Implements
NVec<D1, T>
for a struct which is sort of like a 1-dimensional vector, such as the standardVec<T>
. - Implements
NVecCoreSealed<D1>
for a struct which is sort of like a 1-dimensional vector, such as the standardVec<T>
. - Implements
NVecMut<D1, T>
for a struct which is sort of like a 1-dimensional vector, such as the standardVec<T>
. - Implements
NVec<D, T>
for a struct which is sort of like a 1-dimensional vector, such as the standardVec<T>
, and a dimensionD
which is at least 2-dimensional. - Implements
NVecCoreSealed<D>
for a struct which is sort of like a 1-dimensional vector, such as the standardVec<T>
, and a dimensionD
which is at least 2-dimensional. - Implements
NVecMut<D, T>
for a struct which is sort of like a 1-dimensional vector, such as the standardVec<T>
, and a dimensionD
which is at least 2-dimensional.
Structs§
- Wraps an
NVec<D, T>
into a cached vector which maintains an internal cache. - A cardinality of dimension
D1
vectors, which is simply a length. - A constant vector which returns the same value for any input index.
- One dimension.
- Two dimensions.
- Three dimensions.
- Four dimensions.
- Empty cardinality.
- An empty vector of dimension
D
with no elements. - A variable cardinality, jagged,
D2
vector represented by a tuple of a flatD1
storage and row end indices. - A functional vector of dimension
D
and cardinalityC
havingT
scalar elements. V1<T>
(NVec<D1, T>
) builder.V2<T>
(NVec<D2, T>
) builder.V3<T>
(NVec<D3, T>
) builder.V4<T>
(NVec<D4, T>
) builder.- A rectangular cardinality of dimension
D2
vectors, which is equal to two lengths across each dimensions. - A rectangular cardinality of dimension
D3
vectors, which is equal to three lengths across each dimensions. - A rectangular cardinality of dimension
D4
vectors, which is equal to four lengths across each dimensions. - A sparse vector of dimension
D
. - Unbounded cardinality.
- Builders for multi-dimensional vectors.
- A variable cardinality of dimension
D2
vectors such that every child in every lower dimension can have different numbers of children. - A variable cardinality of dimension
D3
vectors such that every child in every lower dimension can have different numbers of children. - A variable cardinality of dimension
D4
vectors such that every child in every lower dimension can have different numbers of children.
Enums§
- Result of an
card_equality
check of two vectors of the same dimension. - Result of an
equality
check of two vectors of the same dimension. - Indices that are less than or equal to dimension 0.
- Indices that are less than or equal to dimension 1.
- Indices that are less than or equal to dimension 2.
- Indices that are less than or equal to dimension 3.
- Indices that are less than or equal to dimension 4.
- An index that can never be created or used to call an element or cardinality of a vector; used as a boundary condition on the recursive dimension types.
Traits§
- A simple map of indices to values.
- Cardinality of a vector.
- Union of indices that can be used to query cardinality of any lower level dimension of a vector with dimension
D
. - Dimensionality of a structure, such as D1 for one-dimensional or D2 for two-dimensional structures.
- Converts an
NVec<D, T>
into a cached vector which maintains an internal cache. - A type that can be transformed into the standard index of dimension
D
. - Transforms a
D1
vector into a jaggedD2
vector viainto_x
methods; or alternatively, creates a jaggedD2
vector viewas_x
methods. - Union of indices that are less than or equal to dimension
D
. - A map of indices to values.
- A
D
dimensional vector. - Core & common functionalities of vectors.
- A
D
dimensional mutable vector. - A type alias:
V1<T>
is equivalent toNVec<D1, T>
. - A type alias:
V2<T>
is equivalent toNVec<D2, T>
. - A type alias:
V3<T>
is equivalent toNVec<D3, T>
. - A type alias:
V4<T>
is equivalent toNVec<D4, T>
. - A type alias:
V1Mut<T>
is equivalent toNVecMut<D1, T>
. - A type alias:
V2Mut<T>
is equivalent toNVecMut<D2, T>
. - A type alias:
V3Mut<T>
is equivalent toNVecMut<D3, T>
. - A type alias:
V4Mut<T>
is equivalent toNVecMut<D4, T>
.
Type Aliases§
- Default type used as the cache of cached vectors.
- Default type used as the lookup of sparse vectors.