Why a medium is not transmitting, when the answer is “not yet”.
The case #49 calls sharpest, and the reason it is in v1 rather than deferred
with the rest: a compliant EU868 backend must block in send for up to
~99 s, and an operator watching queue_depth climb cannot tell
“duty-cycle limited” from “radio dead”. SimMedium::slide_to_contact already
blocks for exactly this reason and ContactWindow::wait_at already computes
the number, so this is a producer that exists rather than a keyspace row
waiting for hardware.
Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.
Zero while available is false means the medium is
blocked and does not know for how long, which is a different answer from
“blocked for 0 ms” and a real state for a device that can say it is busy
without saying when it will not be.
The medium would not, and this is how long until it would.
Two named constructors rather than one taking (bool, u64), because the
two states are what a caller is choosing between and a boolean argument
at a call site says nothing about which way round it goes.