mirror of
https://github.com/block/buzz.git
synced 2026-08-18 06:50:31 +02:00
docs(terminal): keep split slicing mutations package-scoped
Co-authored-by: npub1mprnacetjua2xx3p5eddmhxyk6wv929ymm5py8kd2xfxurxahspqqlgyta <d8473ee32b973aa31a21a65adddcc4b69cc2a8a4dee8121ecd51926e0cddbc02@buzz.block.builderlab.xyz> Signed-off-by: npub1mprnacetjua2xx3p5eddmhxyk6wv929ymm5py8kd2xfxurxahspqqlgyta <d8473ee32b973aa31a21a65adddcc4b69cc2a8a4dee8121ecd51926e0cddbc02@buzz.block.builderlab.xyz>
This commit is contained in:
parent
86af878301
commit
8515026860
@@ -1,6 +1,15 @@
|
||||
//! The work-denominated slicing seam: what bounds one lock hold, what bounds
|
||||
//! the queue behind it, and what proves the work was actually done.
|
||||
//!
|
||||
//! **This is half a suite.** The adversarial resize and overflow cases live
|
||||
//! in `slicing_adversarial.rs`, split out for the file-size ratchet; the two
|
||||
//! files are one set of contracts. A mutation check scoped with
|
||||
//! `--test slicing` covers 20 of 76 package tests and can report a confident
|
||||
//! pass while the killing fixture sits in the sibling file. Dropping the
|
||||
//! scrollback debt does exactly that, then dies under the package.
|
||||
//!
|
||||
//! Mutation checks run the package, never a file: `cargo test -p buzz-terminal`.
|
||||
//!
|
||||
//! Every assertion here is an **exact** expected value, never a `> 0`. A fix
|
||||
//! that bounds the lock by *dropping* work instead of deferring it reports a
|
||||
//! beautiful latency and a perfect screen-content receipt -- DECALN fills the
|
||||
|
||||
@@ -1,4 +1,13 @@
|
||||
//! Adversarial slicing cases for resize debt, oversized atoms, and arithmetic extremes.
|
||||
//!
|
||||
//! **This is half a suite.** The remaining work-bound cases live in
|
||||
//! `slicing.rs`; the two files are one set of contracts split only for the
|
||||
//! file-size ratchet. A mutation check scoped with `--test slicing_adversarial`
|
||||
//! covers 4 of 76 package tests and can report a confident pass while the
|
||||
//! killing fixture sits in the sibling file. Sizing from the whole budget does
|
||||
//! exactly that, then dies under the package.
|
||||
//!
|
||||
//! Mutation checks run the package, never a file: `cargo test -p buzz-terminal`.
|
||||
|
||||
use buzz_terminal::fences::{
|
||||
max_atom_work, max_drain_work, slice_bytes_remaining, Fences, WORK_BUDGET,
|
||||
|
||||
Reference in New Issue
Block a user