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

Revisit the design of get_matrix3d #33

Open
furgalep opened this issue Jun 22, 2014 · 0 comments
Open

Revisit the design of get_matrix3d #33

furgalep opened this issue Jun 22, 2014 · 0 comments

Comments

@furgalep
Copy link
Contributor

I've noticed that, for every eigen type, one has to reimplement class get_matrix3d. This seems error prone and tedious. For example, if we want to support transformation of 4x1 types (see #30), we will have to also implement class get_matrix4d in every type. Then if we want to support native dynamic matrices (see #29), we would have to implement something similar in every derived rotation type as well.

Can we find a simpler way that only needs one implementation per linear algebra package?

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

1 participant