Mike Boutin

For code using the macros in a 2018 crate, probably! I'm not sure if this would also support 2015 edition.

It may also be time to drop 2015 edition support. Perhaps coinciding with the release of 2021 edition?

This would likely be part of a `uom` 2.0. I've started looking into it in the [`dev-macros`](https://github.com/iliekturtles/uom/tree/dev-macros) branch.

While it is messy, if it works it could be a good way to have a short-term solution until I make more progress on the dev-macros branch.

@chrysn I believe you can do that now by using `bigrational` as the underlying storage type. The downside of this approach is that all mathematical operations are going to be...

Note to myself to review `PhantomData` variance: * https://doc.rust-lang.org/nomicon/phantom-data.html#table-of-phantomdata-patterns * https://doc.rust-lang.org/reference/subtyping.html#variance

MSRV bump will happen when #260 is merged.

Is the try-from feature still needed?

I haven't really thought down the path of `ConstConversion` + `Conversion`. How would the two traits would? Would we have two different code paths for const/non-const? As an aside I'm...

This would definitely be a good feature to have (PRs welcome)! ```rust let one_meter = 1.0 * uom::si::length::meter; ``` I believe this could be implemented with something like the following...