Removing the FrequencyUnit.BUnit - #1529
Conversation
angularsen
commented
Mar 29, 2025
Just so I understand, we are removing this unit due to using In a way, I don't like the idea of removing something that someone actually requested and added, although yes it does seem very domain specific and I can't find much about this unit online. I can get behind removing it for the reason that it is not widely used, but I have a feeling we'll need to support functions like Sqrt, Sin, Cos etc at some point anyway. Can we easily make exceptions for units like these? |
lipchev
commented
Mar 29, 2025
The idea is that a unit conversions should be reversible, as such they cannot use irrational functions (I'm 99% sure there is format definition about it). I don't see where it says that we need to support (now or in the future) If you want the |
lipchev
commented
Mar 30, 2025
Here's another way of looking at this: having an expression such as |
angularsen
commented
Mar 30, 2025
Useful insight regarding operations vs unit conversions. I don't know of any definitions regarding rules for only allowing rational unit conversions, can't find any with a quick google. Won't all logarithmic units be disallowed then? I tried to think of examples with PI, but realize these are probably operations like you say, converting radius to area or circumference. Anyway, we can remove this. Mostly because it is not widely used, maybe because it violates some unit definition rule, and probably because it is actually an operation and not a unit conversion. |
lipchev
commented
Mar 30, 2025
The |
Removing the
FrequencyUnit.BUnit.As discussed in #1393 (comment)