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

Why make the Octree not copyable and assignable? #1

Closed
Nathaniel-Han opened this issue Sep 15, 2015 · 1 comment
Closed

Why make the Octree not copyable and assignable? #1

Nathaniel-Han opened this issue Sep 15, 2015 · 1 comment

Comments

@Nathaniel-Han
Copy link

No description provided.

@jbehley
Copy link
Owner

jbehley commented Sep 17, 2015

Question: Why is the octree not copy or assignable?

In my opinion, one usually does not need to copy an octree or assign it to anorher octree. The octree can be passed as reference and therefore a copy is usually not needed.

In regard to the performance, a copy or assigning always needs a deep copy and there we would have to decide if we also copy the points used to initialize the tree.

@jbehley jbehley closed this as completed Oct 25, 2015
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

No branches or pull requests

2 participants