lipchev

> 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. > >...

Hello guys, Here's how I was able to consistently reproduce the issue (it's either the operation exception, an `invalid BLOB handle` or a deadlock..): I've created a simple benchmark in...

I wouldn't say it's an invalid use case- just not supported (note that I couldn't find any docs regarding the behavior of the Async methods). Given how much slower it...

@angularsen @tmilnthorp @Muximize Hey guys, don't mean to push, but It would be helpful if we could have a discussion about the changes proposed in this PR. Specifically, if we...

> 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? Yeah, sorry I wasn't clear: what I...

I fear this would require a ton of code duplication (code-gen, tests, serialization and all custom code related to the affected interfaces) as well as the increased contribution effort of...

Alternatively, we could make yet another "experimental" branch (e.g. v6-fractions) - but we still have to pick one of the proposed options to implement :)

@angularsen I think the code is almost good- there a few more internals to optimize, but as far as the public API I think this cover all changes. I've updated...

Yes, but this is not the same as having the _short_ attribute visible as per the _Label text settings_, while the _longer_ one appears on mouse over.

``` var asFirstUnit = other.GetValueAs(this.Unit); var asSecondUnit = GetValueAs(other.Unit); return (_value.CompareTo(asFirstUnit) - other.Value.CompareTo(asSecondUnit)) / 2; ``` The idea was that the rounding error may only occur in the one direction...