-
Notifications
You must be signed in to change notification settings - Fork 286
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
Joint has the default copy constructor #524
Comments
It's definitely not intentional, and it's definitely dangerous. I'll submit a pull request to correct this later today. |
It's also worth checking if this is an issue for BodyNode and Skeleton, since none of those should permit a copy construction. |
|
I'm pretty sure they'd technically be deleted by default since they inherit from a class whose copy constructor is deleted. Still, it would be good to be explicit about it. |
They're not - I discovered this because I'm using |
|
This seems to be resolved by #539. |
I noticed that
Joint
does not= delete
its copy constructor. I believe that all of the fields inJoint
are copyable, so this means that the default copy (and, possibly, move) constructor is being implicitly defined by the compiler.I suspect that is not intentional (and potentially dangerous!) because every
Joint
is supposed to be owned by it's childBodyNode
.The text was updated successfully, but these errors were encountered: