Minor suggestion: allowing the use of integer (or why not?) about quaternion HOT 3 CLOSED

Keeping the array as integers would require creating all new quaternion_int datatypes. And I can think of absolutely no good reason to do so. (Mathematica<<Quaternions, I'm looking at you!) But it is trivial to automatically convert an array input to this function. This does require copying when the input is an int array, but it can't be avoided because that's just not how statically typed languages like C work — and of course, standard python, numpy, and this module are C under the covers.

from quaternion.

though as_quat_array isn't a math function, is there a reason for requiring exclusively floats?
How about accepting int as well?

Keeping the array as integers would require creating all new quaternion_int datatypes

Though my title may have suggested otherwise, I didn't mean to have a quaternion_int dtype, what I was actually suggesting is expressed in your commit "cast to float when converting ...".

Mathematica<<Quaternions, I'm looking at you!

I'm not sure what you mean here, I'm not using Mathematica and never have.

from quaternion.

PS: I salute your prompt replies and dedication to your quaternion module.

from quaternion.