From what I see, all values can be negative and we should check this case.

Another thing that would be good to do is avoid using i64 and only when creating the Duration to cast the value to i64.

This will give us only 1 place where we should check if we can cast e.g. u32, u64 to i64.

• Please use a different value for the number, e.g. u8 will also be sufficient.

i64 makes easier following conversion to Duration (as Duration accepts i64).

It would be better to fail value parsing as early as possible.

And Yes, Duration takes i64, however, we could easily convert it with From: https://doc.rust-lang.org/std/primitive.i64.html#impl-From%3Cu8%3E-for-i64

It's better to parse a mostly correct value, instead of very wrong value. parsing i64 could also take longer and can have bigger impact on constraint device since this first parser can actually succeed event with e.g. negative value.

Even if the architecture is 32 bit, 64 bit numbers are still supported but not by the hardware itself, so are less performant.

Also check for < 0.0 and NaN (https://doc.rust-lang.org/nightly/std/primitive.f64.html#method.is_nan)