Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't clone geometry when given a pointer #198

Merged
merged 1 commit into from
Jan 2, 2024
Merged

Don't clone geometry when given a pointer #198

merged 1 commit into from
Jan 2, 2024

Conversation

evetion
Copy link
Member

@evetion evetion commented Jan 2, 2024

Fixes #196

If given a pointer, do not clone (internal use)
If given a Geometry, clone it (external use)

Note that some methods can be updated/added, for example the GeoInterface convert for MultiPoint will clone unnecessarily, because it goes through the Point constructor.

@evetion evetion requested a review from rafaqz January 2, 2024 08:25
@rafaqz
Copy link
Member

rafaqz commented Jan 2, 2024

Haha I wrote this too just never PRd 😂

Copy link
Member

@rafaqz rafaqz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rafaqz rafaqz merged commit 350152f into master Jan 2, 2024
11 checks passed
@rafaqz rafaqz deleted the feat/noclone branch January 2, 2024 15:53
rafaqz pushed a commit that referenced this pull request Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why do we use cloneGeom for every output?
2 participants