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
Add missing cols/rows constants #491
Conversation
i vote yes, then #441 can be unified (instead of separate handling for vector and matrix). |
But as row vectors or column vectors? |
iirc, they should be column vectors by default, i.e. vec4 is a mat1x4. |
Actually, the spec says that it depends on whether the vector is the left or right operand in a vector/matrix multiplication. Nowhere does it otherwise refer to the notion of a row vector or column vector. |
that is correct in a general sense but given |
Let's see what @Groovounet has to say. |
...so what do you have to say, @Groovounet? I'm fine with the metaprogramming stuff being moved to a separate file, but until this PR is merged in I can't pull in the latest GLM changes (because I need this fix for my project). |
Notice me, senpai~ |
@Groovounet Can you take a look at this bugfix, please? |
@Groovounet Hi. Do you like this change set? |
I made a branch today type_trait where I investigated. Somehow there are build errors with Visual Studio. |
Seriously? Christ. I'll take a look over the weekend. |
For your information, it was already broken before your changes. I came up with a workaround (in the branch) but I don't know whether it is good. |
All right, thank you for taking a look at this pull request. |
Should I add anything like
rows
orcols
to the vector type traits? Because they can be treated as either column vectors or row vectors, so I dunno...