refactor: derive Debug on WAL types

Deriving debug is highly encouraged so that Result::unwrap() and friends
can print the state of an object if it is causing a panic (it's
impossible to call unwrap() otherwise!)
pull/24376/head
Dom Dwyer 2023-02-22 15:46:05 +01:00
parent 0b424888fd
commit c72c9d2dba
No known key found for this signature in database
GPG Key ID: E4C40DBD9157879A
1 changed files with 2 additions and 0 deletions

View File

@ -389,11 +389,13 @@ impl std::fmt::Debug for Wal {
}
}
#[derive(Debug)]
struct Segments {
closed_segments: BTreeMap<SegmentId, ClosedSegment>,
open_segment: OpenSegmentFileWriter,
}
#[derive(Debug)]
struct WalBuffer {
ops: Vec<SequencedWalOp>,
notify_flush: tokio::sync::watch::Sender<Option<WriteResult>>,