1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
//! Synthetic Unity files built in code, for unityrs tests.
//!
//! Everything here is made from scratch by the builders: never game data,
//! never bytes copied from a real file. The builders return `Vec<u8>` and
//! know nothing of `unityrs-core`, so core's own tests can use them (but
//! for `core_counters`, under the `test-counters` feature alone).
//!
//! Owners (docs/plans/core.md section 7): [`writer`], [`rng`],
//! [`public_types`] (the `Send + Sync` source scan the crates' tests share)
//! and [`waits`] (the no-thread, no-wait source scan) are the scaffold's
//! (implemented); [`blob`], [`serialized`] and [`bundle`] are package C's;
//! [`env`](mod@env) is package D's; [`depth`] (the deep values of plan
//! section 3.10), [`counted`] (the counting global allocator, and the
//! thread it counts), [`guard`] (the deadlock guard of every test that
//! hands work between threads), [`stack`] (the child-process probes that
//! measure a stack, and tell an overflow from every other failure) and
//! [`child`] (how every test runs a child process: a `SIGKILL` from
//! outside is no result) and [`scratch`] (how every test's scratch is
//! removed, whatever happens to the test or its child) are package B's;
//! [`ledger`] (one coherent observation of a counted engine's heap and
//! charges) and [`search`] (a limit's need, its monotonicity checked) are
//! the memory gates' (`docs/plans/extract.md` X12, X13); [`address_space`] (the cap that makes the C allocator
//! refuse, for the tests of liblzma's own allocations) is package C's;
//! [`mutate`] (G3b's mutator) is the integration's; [`fuzz`] (the fuzz
//! targets' input layouts, which `examples/fuzz_seeds.rs` writes the seeds
//! in) is the fuzz package's; [`ngui`] (the NGUI-shaped atlases the cutter's
//! reference, `tools/parity/ngui_cutter.py`, is tested and recorded on) is
//! P1b's.
pub use Rng;
pub use ByteWriter;
/// The core's test-only counters (`docs/plans/batch.md` section 6, CR8),
/// under this crate's `test-counters` feature, which turns the core's
/// feature of the same name on for every crate a test build links. The
/// core's own unit tests read `unityrs_core::testing` instead: theirs is
/// the core built for the test, this the library build's.
pub use testing as core_counters;