Files
lix/lix/libutil
Raito Bezarius f8ccd9d572 libutil/async-io: augment read type safety w.r.t to EOFs
Usually, EOFs are represented by returning 0 in the `read` APIs, at
least, this is what read(2) dictate.

As clever creature, we may sum zeroes sometimes (advanced form:
`buf->added(got)`) and forego handling the EOF condition.

To avoid the bug that lurked in remote-store.cc and caused busy looping
if the remote end disconnects suddenly, we return
`Result<Option<size_t>>` forcing the caller to perform a specific
processing for the EOF situation.

The conversion did not raise any other offending code path.

Change-Id: I185fdcb77aa82d87ab0802d66ac37c1363657a73
Signed-off-by: Raito Bezarius <raito@lix.systems>
2025-07-23 10:35:37 +00:00
..
2025-03-03 20:48:59 +01:00
2025-03-03 20:48:59 +01:00
2025-02-23 17:18:48 +00:00
2025-03-23 20:42:39 +00:00
2025-02-22 18:33:51 -08:00
2025-04-24 13:48:15 +00:00
2025-06-11 18:11:57 +00:00
2025-06-11 18:11:57 +00:00
2025-05-03 23:16:48 +02:00
2025-04-08 12:13:42 +00:00
2025-05-19 15:35:52 +02:00
2025-04-24 13:48:15 +00:00
2025-04-24 13:48:15 +00:00
2025-04-24 13:48:15 +00:00
2025-01-19 09:55:10 +01:00
2025-07-07 18:13:16 +00:00
2025-03-05 18:49:45 +01:00
2025-04-24 13:48:15 +00:00
2025-04-24 13:48:15 +00:00