Mosè Giordano

> We just have to remember that temperature deltas are in kelvin. I'm not sure I agree on this. Summing two absolute temperatures doesn't often make sense even when using...

> See #137 All examples I can find there (like your comments [here](https://github.com/ajkeller34/Unitful.jl/issues/137#issuecomment-431398366) and [here](https://github.com/ajkeller34/Unitful.jl/issues/137#issuecomment-431902689)) are related to the fact that combining Kelvin and degree Celsius is ill-defined, and I...

You need to [broadcast](https://docs.julialang.org/en/v1/manual/arrays/#Broadcasting) the function: ```julia julia> using Unitful julia> a = [1,2,3]u"ft" 3-element Vector{Quantity{Int64, 𝐋, Unitful.FreeUnits{(ft,), 𝐋, nothing}}}: 1 ft 2 ft 3 ft julia> uconvert.(u"inch", a) 3-element...

And "cycle" is already in [`UnitfulAngles.jl`](https://github.com/yakir12/UnitfulAngles.jl) as "turn"

Indeed the algorithm used in `generic_lufact!` doesn't look very physical-units-friendly: ```julia Akkinv = inv(A[k,k]) for i = k+1:m A[i,k] *= Akkinv end ``` Other types for which `T` and `T*inv(T)`...

For the time being I'd avoid splitting the discussion and continuing in rigetti/Unitful.jl, I believe the situation is still unclear

Related to #379 probably?

> since div should always return an integer and never a dimensionful quantity. Why? :thinking: I think such change would also be breaking, thus forcing us to go to v2

Thank you! I like your approach to avoid type collision. I might have some time to bake a PR, but not anytime soon.

It'd be good to have a getter function for the `val` field just as a nicer interface than `a.val`. This function would be semantically different from `ustrip`, and probably won't...