> rotors some form of Rotor3 may stick around for optimization purposes.
i just pushed multivectors in R^2 and R^3 and changed the geometric products to produce those. however i noticed the tutorial code for rotors is abridging the math somewhat. they are supposed to carry the vectors along with them but because they are fixed to the basis planes they are constant so they are not stored and are clipped out of the math. the 'correct' multivector format (according to euclideanspace.com) has to carry the vectors and those also participate in reversal operations. addition/subtraction is elementwise, so adding two multivectors does also alter the planar spaces. for an interactive simulation (games) we just need to spin and possibly move something so a handful of these assertions are useful (ex. how the trivector is always zero when the basis planes are used to do a double reflection to rotate.) i haven't done the inner/outer products on the multivector type yet. those are needed to change grades (and implement the Rotor without the special rotor module.)
