Type Safe Units of Measure

A series of type definitions and monads written in C# for enforcing type safety between units of measures and providing compile-time type checking of operations on units of measure. Additionally, it provides automatic conversion between common unit standards.

Unfortunately, this code is a little obtuse because of how C# generics work. There is no good way to make a class generic to numbers, so I've punted and just made everything a double precision floating point.

The library is meant to strictly encode every interaction between classes of units. For example, while it is obvious that one should not add a Mass to a Velocity, it's less obvious that one should not add a Velocity to a Velocity. The correct operation is to add a Change in Velocity to a Velocity. Subtracting two Velocities will give a Change in Velocity in return. Dividing a Change in Velocity by a Change in Time should result in an Acceleration. Multiplying an Acceleration by a Change in Time should result in a Change in Velocity.

Examples

Accelerate an object that is in motion

// setup an object with physical properties
var accel = new Acceleration<Feet, Seconds> { Value = 10 };
var spd = new Velocity<Feet, Seconds> { Value = 3 };
var disp = new Feet { Value = 376 };

// calculate the change over time and apply the changes
var time = new Seconds { Value = 5 };
Delta<Velocity<Feet, Seconds>> dspd = accel.Multiply(time);
spd = dspd.Add(spd);
Delta<Feet> ddisp = spd.Multiply(time);
disp = disp.Add(ddisp);

Assert.AreEqual(50, dspd.Value);
Assert.AreEqual(53, spd.Value);
Assert.AreEqual(265, ddisp.Value);
Assert.AreEqual(641, disp.Value);

Convert Feet to Meters

var feet = new Feet { Value = 35 };
Meters meter = feet;
Assert.AreEqual(10.668, meter.Value, 1e-10);

Calculate the Cosine of an angle in Degrees

var d = new Degrees { Value = 45 };
var v = d.Cos();
Assert.AreEqual(Math.Sqrt(2) / 2, v);

Halp!

I'm a programmer, not a physicist. I have a good handle on arithmetic and other fields of mathematics, but my recollection of the physical properties and their relationships is rusty. I could use some help building the code out to fulfill as much as possible, and to make sure the semantics of some of the composite types make sense.