Add methods to release objects owned by some Geometry types #401
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.
This can allow for more efficient implementation implementation of some
operations such as GeometryCombiner. Objects that release their
components are left in an undefined state. This approach is taken
because it is analogous to the state of moved-from objects, and because
reverting the objects to a defined state can be expensive. For example,
an empty Polygon must own an empty LinearRing, which must own an empty
CoordinateSequence.