For Discussion: Using tinyvec::ArrayVec for Position without allocating
#218
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CHANGES.mdif knowledge of this change could be valuable to users.This is a PR for discussion. I've moved
Positionfrom being aVec<f64>to being anArrayVec<f64>with a capacity of 4 elements (x, y, z, t). This means that instead of every point resulting in an allocation, we only allocate to createLineString,Polygonetc.Preliminary cargo-bench results suggest performance improvements up to 79% in some cases.
If there is agreement that this is a good direction, I'll add some convenience functions like
Position::from_vecetc to recover some of the ergonomics of working with Vecs.Benchmarks: