Mateusz Pusz

> IIUC, they're inter-comparable, so they must be of the same kind. The rules you quote are for the ISQ quantities and not units 😉 Often, natural units are about...

This also affects other definitions of popular unit systems. For example: ```cpp namespace si { inline constexpr struct kilogram : decltype(kilo) {} kilogram; } namespace non_si { inline constexpr struct...

Sure, freestanding is our target as stated here https://wg21.link/p3045#low-standardization-cost and as I explicitly said several times before (https://github.com/mpusz/mp-units/discussions/406, https://github.com/mpusz/mp-units/issues/7).

We are removing the support for inheritance from other system entities.

Initially, we tried to isolate IO as much as possible (separate CMake targets, separate C++ modules, etc.), but it didn't scale. I consulted the best freestanding experts in the ISO...

This would be great @kwikius! As of now we don't use any conditional compilation for freestanding. We need to decide if we should introduce custom flags or use those used...

More info on text output can be found in https://mpusz.github.io/mp-units/2.2/users_guide/framework_basics/text_output/#derived-unit-symbols-generation

`quantity::zero()` can't be totally removed as it still has some use cases. For example: https://github.com/mpusz/mp-units/blob/99bec8ecbb9dbebc9cfa6c7c1893cd70c9630485/example/glide_computer_lib/glide_computer_lib.cpp#L48-L49

Should `zero` be limited only to addition, subtraction, and comparison? Or maybe the following should also be a thing: ```cpp static_assert((1 * m *= zero) == zero); static_assert((1 * m...

It seems that there are also some cases where `zero` should not be used even though it probably was meant to simplify such cases: https://github.com/mpusz/mp-units/blob/99bec8ecbb9dbebc9cfa6c7c1893cd70c9630485/example/capacitor_time_curve.cpp#L42 https://github.com/mpusz/mp-units/blob/99bec8ecbb9dbebc9cfa6c7c1893cd70c9630485/example/unmanned_aerial_vehicle.cpp#L134