Axis/Direction Normalization

[gottfriedleibniz]

In certain places through this library, I've noticed the branching from the internal/implicit normalization can cause a pretty big hit in otherwise pipeline-friendly code. For example:

• glm_quatv
• glm_quat_for
• glm_rotate_make
• glm_quat_rotatev: this case is slightly different than others.

I was wondering if (A) anybody else has experienced/measured this; and (B) would it be possible to introduce functions (or something else, e.g., a build option) that assume these 'axis' or 'direction' parameters are already normalized.

Edit: Clarity.

[Recep Aslantas]

would it be possible to introduce functions (or something else, e.g., a build option) that assume these 'axis' or 'direction' parameters are already normalized.

Actually that would be nice, if passed axis and direction are already unit / normalized that would be redundant and extra overhead to normalize them again :(

Any suggestions? Maybe we could provide alternative functions plus build configuration to change existing behavior if it is desired

[gottfriedleibniz]

Any suggestions?

Breaking backwards compatibility :). Otherwise, what you suggest seems fine.