Sebastian Stock

An even more confusing example (this one could return `𝐋` or error, but it definitely shouldn’t return `NoDims`): ```julia julia> dimension(Unitful.Length) NoDims ```

There is a plan to normalize `ℏ` to `ħ`: https://github.com/JuliaLang/julia/issues/48870 If this is implemented, `Unitful.ℏ` and `Unitful.ħ` would automatically refer to the same object (we could still change the printing...

You can use `upreferred` for that: ```julia julia> 1u"cm" / 5u"m" 0.2 cm m^-1 julia> upreferred(ans) 0.002 ```

Replaced by #606 and #626.

> ### Units in this first ratio don't simplify properly to dimensionless or plain dB, but the calculation is correct > > ratio = max_PFD/pfd_on_ground The package doesn’t automatically simplify...

> ### This second ratio is the inverse of the first and should also be dimensionless: > > inv_ratio = pfd_on_ground/max_PFD > > But it throws a dimension error instead...

It would not be too hard to implement, but it would require to turn `SparseVector` into a `mutable struct` (otherwise you cannot resize it). I think it would be nice...

Another option would be to make the support for non-`Real` types opt-in, so that this package only supports `Exponential{

Currently, units and dimensions are ordered alphabetically (by their full name, i.e., `m` comes before `N` because `Meter` comes before `Newton` alphabetically). This order is used in the internal representation,...

I think it would be good to make the case of different dimensions error instead of returning `false`. The other kind of dimension mismatch (array dimension instead of physical dimension)...