Matty Weatherley

Popping in here to link this [bevy pull request](https://github.com/bevyengine/bevy/pull/12187) where I implemented a general version of this which looks like this: ````rust pub fn align( &mut self, handle: Vec3, direction:...

> Oh and @mweatherley, food for thought: This consumes the `CubicGenerator` from the math crate. First use of splines i've seen "in the wild", might be something to evaluate the...

> Hey cool stuff. However I think it would be important to keep a baked animation data at all times. With curves it's really conveniant to work and modify animations...

> I believe right now the transform values are lerped between previous and next key which will always be the case because of variable frame durations. The lerp function comes...

> I was looking at lib.rs in `bevy_animation ` : `fn apply_single_keyframe()` I believe it's the function used for apply animations but I'm not sure I just guess it by...

> Very cool! Obligatory note that we cannot merge this without profiling. Well, I did profile it, but as noted in the description, *more* profiling would definitely be great.

> The proposal looks great so far. Some thoughts: > > 1. Since these curves are general purpose rather than specifically targeting animation, I see a lot of value in...

> Also do we want this to be general enough to capture parametric surfaces? Because I think we can do this if T is not Ord (a Vec2 for example)....

A random thought on the range business: we could implement our own `Copy` version of ranges (say, `T`), and then use `impl Into` or `impl TryInto` together with a corresponding...

> > Rust's Range types are not Copy > > FYI, this is slated to change over either the 2024 or 2027 edition boundary: https://github.com/pitaj/rfcs/blob/new-range/text/3550-new-range.md That's good to know! Honestly,...