Yves Delley

Anyway, with class 4 ruled out, it is indeed a matter of judgment if these things are distinct enough to warrant further division. If we can have a `representation_cast` I'm...

Indeed, I would reclassify the above as - `static_cast(q)` -> may truncate, but not reinterpret physical type information - `static_cast(q)` -> may truncate, but not reinterpret physical type information -...

Ah, but then we are missing something, no? How would I spell a cast that goes from `quantity` to `quantity` without me having to spell the `metre`?

> Physical type information is always perceived. Not with `reintrepret_cast(h = 1*m)`.

What unit is `Gal`? I did read that as "Gallon" which I would have considered class 4...

I think there is a point to this proposal, but IMHO it needs to be approached with care. After all, even if we just look at the standard `static_cast`, `reinterpret_cast`...

I'll start with the quick fixes. Then I guess I should strive for a proper implementation of the temperature things, as it may impact the internals of the `point_origin` a...

@mpusz and @johelegp: I'd like to hear your input regarding "identity" and "equivalence" of different `point_origin`. The reason is, I really would like to associate each `point_origin` with a dimension,...

Hey guys, just to let you know, this is not forgotten! A project has just jumped in priority, so I probably won't be able to work on this for the...

Hey @mpusz, no worries - we al know how it goes. This feature is dear to my heart (as is this library in general), so I definitely intend to bring...