Mateusz Pusz

Should we complicate the generic unit symbol printing framework (i.e. additional constructors and fields in `basic_symbol_text`) to implement this single exception? Or maybe we should just provide a custom formatter...

I would love to but this is not that easy. I was in the LEWG room when we discussed P1745 and I am fully aware of the naming conventions in...

I did an approach to this subject and found the following issues: - `bitrate` and `information` actually is a problem as we have such aliases already - I do not...

I must admit it has some good points. It is verbose thus easy to understand and unambiguous. However, it is inconsistent with what ISO C++ Committee decided for concepts in...

> I have re-read P1754R1 and the only reference to prefix and suffix is in 1.1.2. I was not referring to the paper but to the discussion that we had...

As I wrote, there was a long discussion about this. We always want to somehow mark "a new thing" as we are not to use it, we are a bit...

Thanks @foonathan! Yes, it seems is a full list of problematic framework types. However, there are some other potential conflicts there. For example: https://github.com/mpusz/units/blob/dcbadfe285b9fbe6357604537ae7d44d430f84c8/src/include/units/data/information.h#L48-L52 I like your suggestions about adding...

> How? OK, maybe I was wrong and one step ahead. At least for now, with the [dowcasting facility](https://mpusz.github.io/units/design/downcasting.html) working as it is now, the end-user is nearly never facing...

> maybe type quantity could be renamed to basic_quantity following precedent of std::basic_string and free up quantity for the concept? This actually will always be visible to the user. For...

Thanks for pointing that. Anyway, over time I changed my initial plans here. I do not think that Modules with granularity smaller than the entire system are a good idea....