a8b9c945c7
# Objective - Contributes to #15460 ## Solution - Added two new features, `std` (default) and `alloc`, gating `std` and `alloc` behind them respectively. - Added missing `f32` functions to `std_ops` as required. These `f32` methods have been added to the `clippy.toml` deny list to aid in `no_std` development. ## Testing - CI - `cargo clippy -p bevy_math --no-default-features --features libm --target "x86_64-unknown-none"` - `cargo test -p bevy_math --no-default-features --features libm` - `cargo test -p bevy_math --no-default-features --features "libm, alloc"` - `cargo test -p bevy_math --no-default-features --features "libm, alloc, std"` - `cargo test -p bevy_math --no-default-features --features "std"` ## Notes The following items require the `alloc` feature to be enabled: - `CubicBSpline` - `CubicBezier` - `CubicCardinalSpline` - `CubicCurve` - `CubicGenerator` - `CubicHermite` - `CubicNurbs` - `CyclicCubicGenerator` - `RationalCurve` - `RationalGenerator` - `BoxedPolygon` - `BoxedPolyline2d` - `BoxedPolyline3d` - `SampleCurve` - `SampleAutoCurve` - `UnevenSampleCurve` - `UnevenSampleAutoCurve` - `EvenCore` - `UnevenCore` - `ChunkedUnevenCore` This requirement could be relaxed in certain cases, but I had erred on the side of gating rather than modifying. Since `no_std` is a new set of platforms we are adding support to, and the `alloc` feature is enabled by default, this is not a breaking change. --------- Co-authored-by: Benjamin Brienen <benjamin.brienen@outlook.com> Co-authored-by: Matty <2975848+mweatherley@users.noreply.github.com> Co-authored-by: Joona Aalto <jondolf.dev@gmail.com>
58 lines
2.2 KiB
Rust
58 lines
2.2 KiB
Rust
//! Iterable curves, which sample in the form of an iterator in order to support `Vec`-like
|
|
//! output whose length cannot be known statically.
|
|
|
|
use super::Interval;
|
|
|
|
#[cfg(feature = "alloc")]
|
|
use {super::ConstantCurve, alloc::vec::Vec};
|
|
|
|
/// A curve which provides samples in the form of [`Iterator`]s.
|
|
///
|
|
/// This is an abstraction that provides an interface for curves which look like `Curve<Vec<T>>`
|
|
/// but side-stepping issues with allocation on sampling. This happens when the size of an output
|
|
/// array cannot be known statically.
|
|
pub trait IterableCurve<T> {
|
|
/// The interval over which this curve is parametrized.
|
|
fn domain(&self) -> Interval;
|
|
|
|
/// Sample a point on this curve at the parameter value `t`, producing an iterator over values.
|
|
/// This is the unchecked version of sampling, which should only be used if the sample time `t`
|
|
/// is already known to lie within the curve's domain.
|
|
///
|
|
/// Values sampled from outside of a curve's domain are generally considered invalid; data which
|
|
/// is nonsensical or otherwise useless may be returned in such a circumstance, and extrapolation
|
|
/// beyond a curve's domain should not be relied upon.
|
|
fn sample_iter_unchecked(&self, t: f32) -> impl Iterator<Item = T>;
|
|
|
|
/// Sample this curve at a specified time `t`, producing an iterator over sampled values.
|
|
/// The parameter `t` is clamped to the domain of the curve.
|
|
fn sample_iter_clamped(&self, t: f32) -> impl Iterator<Item = T> {
|
|
let t_clamped = self.domain().clamp(t);
|
|
self.sample_iter_unchecked(t_clamped)
|
|
}
|
|
|
|
/// Sample this curve at a specified time `t`, producing an iterator over sampled values.
|
|
/// If the parameter `t` does not lie in the curve's domain, `None` is returned.
|
|
fn sample_iter(&self, t: f32) -> Option<impl Iterator<Item = T>> {
|
|
if self.domain().contains(t) {
|
|
Some(self.sample_iter_unchecked(t))
|
|
} else {
|
|
None
|
|
}
|
|
}
|
|
}
|
|
|
|
#[cfg(feature = "alloc")]
|
|
impl<T> IterableCurve<T> for ConstantCurve<Vec<T>>
|
|
where
|
|
T: Clone,
|
|
{
|
|
fn domain(&self) -> Interval {
|
|
self.domain
|
|
}
|
|
|
|
fn sample_iter_unchecked(&self, _t: f32) -> impl Iterator<Item = T> {
|
|
self.value.iter().cloned()
|
|
}
|
|
}
|