Mateusz Pusz

As stated above right now `torque` is defined in terms of an `angle`: https://github.com/mpusz/units/blob/8632ac1461ef3188ac748d51540b48f4fb7199b0/src/include/units/physical/si/derived/torque.h#L35 This makes it incompatible with `energy` and no cast will help here. However, this should be...

> By 4), I referred to quantity_cast(1_s). Might I have gotten that one wrong, and it's in fact prevented by the equivalent requirement? Indeed. It will not work. You cannot...

My understanding is that we have: - representation casting -> may truncate - unit casting -> may truncate when the unit has a smaller resolution or involves truncating conversion factor...

OK, I missed a "new" one 😉 Anyway, I think that all of them are of similar "severity" and I do not see a possibility to introduce multiple categories here.

```cpp representation_cast(q); representation_cast(q); representation_cast(q); representation_cast(q); representation_cast(q); ``` I think this is expressive? I agree that having 4 names (for each type) does not have sense and we can do better....

However, I think that `quantity_cast` is a better name for the above, Although, I am not a native speaker.

What is the difference between `representation_cast(1 * m)` and `reinterpret_quantity_cast(1 * m)`?

There is no such thing like: > reinterpret_cast(q) -> does not change values and should not truncate, but does discard physical type information Physical type information is always perceived. It...

> reinterpret_cast(q) -> does not change values and should not truncate, but does discard physical type information I am not sure about this. As @johelegp mentioned, it will also truncate...

> How would I spell a cast that goes from quantity to quantity without me having to spell the metre? For now, there is no cast that is able to...