A few minutes ago, I wanted to know how many yards there are in a mile. So, I said this:
(1 % Mile) # Yard
In response, I got complaints about an ambiguous LCSU. That makes enough sense, but it sure is exasperating for a user just taking this for a quick spin.
I propose new operators %% and ## that are monomorphic in their LCSU (requiring a DefaultLCSU) to make the above easier. We would export these from Data.Metrology.Mono and could encourage first-time users to try the mono functions first.
See also issue goldfirere/units-defs#2, which discusses related changes to the structure of the SI modules to support monomorphic programming.
A few minutes ago, I wanted to know how many yards there are in a mile. So, I said this:
In response, I got complaints about an ambiguous LCSU. That makes enough sense, but it sure is exasperating for a user just taking this for a quick spin.
I propose new operators
%%
and##
that are monomorphic in their LCSU (requiring a DefaultLCSU) to make the above easier. We would export these from Data.Metrology.Mono and could encourage first-time users to try the mono functions first.See also issue goldfirere/units-defs#2, which discusses related changes to the structure of the SI modules to support monomorphic programming.