When a user learns conv works for temperature, which takes two unit arguments, it sets an expectation that other conversions might also work that way:
-conv c f 20
But when they try another conversion that has a "to" argument that is implicit, it fails:
-conv km mi 11
And then they see an error message that does not clearly state what they did wrong:
Converting to "float" failed for parameter "length".
While the help is clear, the difference in UI is not easily discoverable following by example, which is often how users pick things up, being loath to ever consult documentation except as a last resort. ;)
A better error message might help, and/or some flexibility in the handling of arguments (e.g. 2-unit call signatures for the current single-unit conversions with an implicit "to" unit).
When a user learns
convworks for temperature, which takes two unit arguments, it sets an expectation that other conversions might also work that way:-conv c f 20But when they try another conversion that has a "to" argument that is implicit, it fails:
-conv km mi 11And then they see an error message that does not clearly state what they did wrong:
Converting to "float" failed for parameter "length".While the help is clear, the difference in UI is not easily discoverable following by example, which is often how users pick things up, being loath to ever consult documentation except as a last resort. ;)
A better error message might help, and/or some flexibility in the handling of arguments (e.g. 2-unit call signatures for the current single-unit conversions with an implicit "to" unit).