Because it is not always the case that units can be correctly inferred from context (i.e. the user may have intended to have different units in the first argument), this should not be done. Note that because the example will result in a run-time, rather than compile-time error, add discussion about this case and that implementation environments should make use of unit conversion validation to help warn users at compile-time when this situation occurs. The minimum viable would be to simply provide warnings whenever the implicit conversion from integer/decimal to quantity results in a quantity with a default unit.