pub fn remote_end(code: RemoteCode, sent: bool, charge: Charge) -> RemoteEndExpand description
Whether remote work may outlive a failure reported of the adapter’s own
accord (spec 013, 3.1): when request bytes left the process, the charge
is unknown because nothing established a final one, and the code is
one where no confirmed end arrived. That covers a transport interrupted
after sending and an unparseable answer, and also remote_deadline and
remote_error without a charge: the remote side gave up or failed
without confirming that its work and charges stopped.