low_latency_data_structures/seqlock/mod.rs
1//! Single-writer, multi-reader cell with seqlock-based validation.
2//!
3//! The reader/writer protocol relies on torn reads being well-defined for
4//! `T: bytemuck::AnyBitPattern`: any bit pattern is a valid `T`, so a
5//! materialised torn value is at worst stale or garbled, never undefined
6//! behaviour. The surrounding sequence-number check rejects such reads
7//! before they leave [`Reader::read`].
8//!
9//! See [`new`] for the entry point, [`Writer`] for writing, and [`Reader`]
10//! for reading.
11
12mod lock;
13mod reader;
14mod writer;
15
16pub use lock::new;
17pub use reader::Reader;
18pub use writer::Writer;