Sebastian Stock

> Now, the case of comparing `0.1m` and `10.0cm`, they indeed have (i) the same physical value, but (ii) different _representations_, so it seems to me that such quantities should...

I started a discussion about hashing quantities with different units here: #379.

The powers are not just converted to `Rational` for display, they are actually stored as `Rational`s in the type of the unit. One could write a function to print unit...

The printing can be changed by replacing `Unitful.superscript`. You can either replace the implementation [here](https://github.com/PainterQubits/Unitful.jl/blob/1e3b270fc050aa1d43e119ab8d60d645b5fce01a/src/display.jl#L209) or add a specialized method to your own code: ```julia Unitful.superscript(i::Rational{Int64}; io=nothing) = "^"*string(float(i)) ```

Note that this `superscript(::Float64)` does not work for all values (try `1.0e6`). There is also an unnecessary ` string(superscript(float(i)))` in the `superscript(::Rational{Int64}; io)` method. We could also think about incorporating...

The problem is that `u"1/s"` is a quantity, not a unit. You can use `u"s^-1"` instead: ``` julia> typeof(u"1/s") Quantity{Int64, 𝐓 ^-1, Unitful.FreeUnits{(s^-1,), 𝐓 ^-1, nothing}} julia> typeof(u"s^-1") Unitful.FreeUnits{(s^-1,), 𝐓...

UnitfulUS.jl [actually passes CI](https://travis-ci.org/PainterQubits/UnitfulUS.jl), the badge in the README just points to the CI for the old repository (UnitfulUS was transferred from ajkeller34 to PainterQubits a while ago).

I would suggest to use `Byte` and `bit` instead of `B` and `b`, that way it isn’t breaking.

You only moved the definition of `q`. The definition of `eV` needs to be moved as well, since it uses `q`.

> However, eV is not a constant, but a unit. So I will move it to _under_ the "constants" section, right? IMO, you can also move it into the constants...