Nick

> I think that people actually do not complain about returning such quantities. They complain that we can't call "legacy" functions taking a value with such a resulting type. @mpusz...

> Please let me know your thoughts. My goal has always been generic interoperability with units so that I can check the dimensional consistency of my code while allowing my...

@mpusz : [Here](https://github.com/boostorg/math/blob/develop/include/boost/math/optimization/cma_es.hpp) is an example; [here](https://github.com/boostorg/math/blob/develop/include/boost/math/optimization/differential_evolution.hpp) is another one. N.B.: While trying to distinguish between dimensionless numbers and dimensioned, I actually found an error in the original literature. So...

Let me know if this is the right place to start this discussion, but I've been working on the "interoperability with other libraries" task. I'm now attempting to get the...

Ok, cool. I think I'm beginning to see the mismatch between my expectations and the design. To wit, this library seems to have the goal of extracting the _maximal possible...

> Please note that dimensionless quantities still have units and some of them might be different than one (e.g., percent). I'm now beginning to think this is wrong-although I concede...

> The properties you expect are valid only for a "unitless" quantity, so a dimensionless quantity with the unit one. Excellent; with clear definitions we can make progress. So to...

@breese's work is exactly the way I had in mind to do this.

In my case, there is no hard guarantee that the desired element is strictly after the hint element. There is only a good reason to believe that the desired element...

@CromwellEnage : I saw on the mailing list that you are now looking to maintain this library; could you fix this bug? The fix is in Higham's book Accuracy and...