Add a caveat section in the README.md
This commit is contained in:
parent
91b236d8b3
commit
b8d9ba177c
1 changed files with 6 additions and 0 deletions
|
@ -90,6 +90,12 @@ metrify you do not need to explicitly tell it the unit you are converting to,
|
||||||
because due to its requirements (conversion is always from non-metric to metric)
|
because due to its requirements (conversion is always from non-metric to metric)
|
||||||
it can automatically pick the correct one.
|
it can automatically pick the correct one.
|
||||||
|
|
||||||
|
Why should I use units(1) instead of metrify?
|
||||||
|
---------------------------------------------
|
||||||
|
units(1) includes many more units than covered by metrify, in addition to
|
||||||
|
allowing other conversions than non-metric to metric. It can also be used for
|
||||||
|
calculations involving units, which metrify does not handle outside of addition.
|
||||||
|
|
||||||
Building and installation
|
Building and installation
|
||||||
-------------------------
|
-------------------------
|
||||||
You can build and test out metrify with `cargo run`. If you want to install it
|
You can build and test out metrify with `cargo run`. If you want to install it
|
||||||
|
|
Loading…
Reference in a new issue