tiny.acp.ReaderStatus

1/// A caller uses this snapshot to report how the reader is doing, or to explain why it stopped. The2/// struct records a snapshot of the reader's lifecycle step, sizes and counters. Both3/// `Storage.status` and `Client.readerStatus` return it. The package exports the type as4/// `acp.ReaderStatus`. The lifecycle step is initialization after `init`, steady after `activate`,5/// and teardown after `deinit`.6pub const Status = struct {7    /// The reader's lifecycle step (phase) when the snapshot was taken.8    phase: alloc_phase.capacity.Phase,9    /// The line limit, in bytes.10    message_bytes: usize,11    /// The buffer size, the line limit plus one byte.12    storage_bytes: usize,13    /// The bytes read in but not yet returned as lines.14    buffered_bytes: usize,15    /// Records the longest line seen, capped at the limit (high-water mark), in bytes. The value16    /// equals the limit once a line has run past it. A partial line still waiting for its newline17    /// counts toward this size too, up to the limit.18    high_water_message_bytes: usize,19    /// Records the number of lines rejected for running past the limit. The count stops rising at20    /// the largest `u64`. The first rejection leaves the reader stopped for good (terminal), so in21    /// normal use the count is 0 or 1.22    rejected_message_count: u64,23    /// Reports true once a line has run past the limit, and every later poll fails.24    terminal: bool,25};

1pub const ReaderStatus = reader.Status;