Enable setting coord type when creating mutable arrays #277
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.
Change list
Add
new_with_options
,with_capacities_and_options
, etc that allow defining the coord type of the generated arrays (either interleaved or separated)Convert the existing
first_pass
andsecond_pass
functions for each mutable array into a privatecount_from_iter
that takes in an iterable of geometries (implemented from traits) and anextend_from_iter
that fills geometries into the array, whether or not they've been pre-allocated.So this is exposed to the end user as e.g.
from_line_strings
which takes in a slice ofimpl LineStringTrait
and creates aMutableLineStringArray
with the exact allocations. This makes theFrom
impls super simpleAdd
Default
forCoordType
, setting it toInterleaved