Rewrite Numerics

[SilentPenguin]

With the Sparrow.Numerics implementation, the resulting size of a mathematical operation is defined by the largest dimension of the operands.

This sort of behaviour becomes problematic when working with libraries such as OpenGL that expect a fixed size vector. The engine would be quietly creating and discarding data in the background without the coder knowing.

Under a possible new system Sparrow.Numerics would:

• remain immutable.
• remain type agnostic.
• include objects for sized and unsized numerics.
• allow the addition of new elements by specifying those elements.

Sized objects would:

• be constructed via Vector.Two, .Three and .Four and Matrix.Two, .Three, and .Four.
• be size dependent, and cannot be over or underfilled.
• explicitly convert to unsized counterparts.
• will trigger compiler errors for mismatched dimensions.
• throw a runtime exception for mismatched dimensions with unsized objects.
• contain swizzles that return correctly sized Vectors.

Unsized objects would:

• be constructed via Vector, and Matrix.
• be size independent, they can store any number of elements.
• explicitly convert to sized counterparts.
• throw a runtime exception for mismatched dimensions.
• not contain swizzles.

[SilentPenguin]

I have implemented this as per the above description.

As a side note: Support libraries (such as collision detection) written for sparrow should use the sized versions of these vectors unless variable sizes are permitted. This means any casting error will occur within the programmer's own code. This makes sparrow much easier to consume.