You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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
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:
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.
The text was updated successfully, but these errors were encountered: