Mike Boutin

I took a look at `float_eq` yesterday and it does look pretty good. `uom` uses `approx` for it's own tests which has similar traits (not implemented however, not sure if...

I didn't review `float_eq` closely either so I can't say how favorably it compares to the other crates or how they compare against each other. My main point of hesitation...

`uom` can't currently support arbitrary underlying storage types such as `Complex64`. See #122 for context. Since [`Complex`](https://docs.rs/num/0.4.0/num/struct.Complex.html) is part of `num` adding support for `Complex32` and `Complex64` shouldn't be too...

I wasn't aware of the difference between an US teaspoon and metric teaspoon and just used the NIST reference. The hardest part of adding a metric tea/tablespoon will be deciding...

I think your idea of using the suffixes + deprecation is the way to go. PRs welcome, even if just for the specific `_metric` or `_imperial` units you're looking for....

This is definitely a point that isn't ideal and I haven't put enough effort into finding a great solution yet. Currently `Quantity`'s fields are public so you can use the...

A similar request came up in #212. The easiest solution would be to modify the `quantity!` macro to accept additional non-standard abbreviations. https://github.com/iliekturtles/uom/blob/dcbb8d34d4735701c74f87ff60f7434a9077ca93/src/quantity.rs#L99-L107 ```diff index 25b72cd..03ce0d5 100644 --- "a/D:\\2.txt" +++...

Good suggestion. I'm going to clarify the subject. We'll also want to take a look at any other traits similar traits that could be implemented.

Started looking at this and it isn't possible to implement `Signed` currently. [`Signed`](https://docs.rs/num/0.4.0/num/trait.Signed.html) inherits [`Num`](https://docs.rs/num/0.4.0/num/trait.Num.html) which in turn inherits [`NumOps`](https://docs.rs/num/0.4.0/num/traits/trait.NumOps.html) which in turn inherits `Mul`. `uom`'s quantity can't implement `Mul`...

For your `fn complex_kinematics_things` is the `S` parameter always a quantity (e.g. `Length`, `Time`, `Velocity`, ...) or completely different types (e.g. `Length`, `f32`, )? If you're always using quantities then...