Check jointDense for all the joints

[jcarpent]

No description provided.

[fvalenza]

Do we still need jointDense with the new JointAccessor ?

[nmansard]

Yes indeed. This has a different purpose (enabling virtual inheritance for object-oriented developers).

[jcarpent]

An other question is: do we need jointDense converter for all joint types ?
I do not think so as it is just a copy of the sparse quantity to their dense counterpart, while joint accessor does the same job but avoiding copy.

[nmansard]

I agree with that: we do not need conversion any more.
However, would you also agree that now, automatic conversion should be
possible (from JointVariant to JointDense)?

On 06/16/2016 09:43 AM, Justin Carpentier wrote:

An other question is: do we need jointDense converter for all joint
types ?
I do not think so as it is just a copy of the sparse quantity to their
dense counterpart, while joint accessor does the same job but avoiding
copy.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#119 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAb-CCVIGZmJPd_maIUzEEvFBfgal17Dks5qMP6VgaJpZM4HoiwP.

[jcarpent]

With the new JointAccessor, it is now possible to get the conversion of the sparse spatial quantities to their dense representation.

[jcarpent]

No need this feature in the very near future. Consider this Issue as solved.