Muximize

+1, but this needs to be implemented for all collection filters. I'm using Restangular promises in my $scope, whose collections are undefined before they get resolved. This gives me this...

I rebased this on the latest changes in #1329 which makes it much cleaner. Example of an interesting situation that occurs here, we previously defined: ``` MassFlow.GramPerSecond = Area.SquareMeter *...

Yes, it will work, except we're not sure why the original contributor chose a particular unit for an operator and if it matters, with precision for example. Also, this PR...

Thanks for the explanation! That makes the concept of inferred division a bit harder, given that we currently have: ``` Mass.Kilogram = Density.KilogramPerCubicMeter * Volume.CubicMeter Mass.Kilogram = MassConcentration.KilogramPerCubicMeter * Volume.CubicMeter...

But if the `Little pain` option means `Mass.FromGrams(someMass.Grams) == someMass` won't work, doesn't that defeat the purpose of changing the underlying type?

Hmm, these failing CI tests pass on my machine. Any guidance?

I completely removed `TimeSpan` from `Duration` inference, which is a nice cleanup. Also removed some tests for `TimeSpan` as the left operand. They all still have a counterpart that tests...

I rebased this to clean up the commit history, which should aid in reviewing.

+1, the breaking changes with Power are preventing us from upgrading to v5 without lots of casting. I'd like to applaud @tmilnthorp for his PR efforts.

Alas, we're using the conversion properties in quite a few places so we have to wait for v6. I should have paid attention and protest against this change landing in...