Mike Boutin

My original thought was that option 1 (`ndarray::Array`) would have been the best, but after digging into `ndarray`'s documentation and trying to do a proof of concept I realized that...

Definitely looking to support decibels. There is some work already in progress in #229 that just needs to be pushed over the finish line.

1. This is the best way right now. With a bit of type magic you can make this more reusable. I didn't go digging to see if the `PerQuantity` type...

To add to this when I first started working on `uom` I attempted to implement the relevant operator traits on `Dimension`. I believe I didn't follow through because it didn't...

> I think you meant: Yep, too many changes in the test project and I missed copying over to my reply.

While looking at the latest question I realized a [`recip`](https://docs.rs/uom/latest/uom/si/struct.Quantity.html#method.recip) method is already defined when `V: Float`. If your code meets that constraint you can just use `recip` instead of...

This uncovers a limitation in `uom` where the trait alias for a custom set of base units is not public! I'll submit a PR shortly to resolve this. The fix...

Interseting! A similar macro should be possible in `uom`. I'm imagining something that would take the module names and path to the `Dimension` alias to calculate the resulting dimension. I...

Thanks for taking a look at this! The reason for the `must_use` attributes isn't for function calls within `uom` but external crates calling `uom`'s functions. For example the `si` example...

Awesome, that would be great!