Mateusz Pusz
Mateusz Pusz
@NAThompson, it is not the case for now. There are no implicit conversions from plain numbers to a dimensionless quantity. We had it in 0.8 but removed it for 2.0...
Safety, performance, and user-readability of error messages will always be a priority of this and most other similar libraries. We can discuss specific things, though. For example, we can decide...
According to the official definition, [`dimensionless` quantity (or, to be more precise, `quantity of dimension one`)](https://jcgm.bipm.org/vim/en/1.8.html) is the one for which all the exponents of the factors corresponding to the...
Yes, we could, but I do not think that is a good idea. For chrono it was one exception case. For our library there are plenty of cases like that.
See: https://github.com/sg16-unicode/sg16-meetings#november-29th-2023.
I think that is not an option. The alternative symbol for each Unicode sign has to be explicitly provided so that text logs from one application can be then read...
Exactly! I tried to form a question so that most C++ developers would understand it. I believe that most have heard about ASCII but may have no clue what "basic...
@ChrisRyan98008 stated on LinkedIn: > ... from a general engineering opinion I would like to keep the ascii version. I could foresee uses for it. It is just sometimes too...
@ChrisRyan98008 also suggested: > Maybe you could just do the unicode output but with a units translations output utility layer to ascii. Maybe this would open up the translation output...
Based on the feedback we got, we decide to leave ASCII-only text output.