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
//! `hyalite` — exact, SIMD-accelerated pairwise/database sequence alignment in pure Rust.
//!
//! A reimplementation and improvement of [Opal](https://github.com/Martinsos/opal)
//! (Rognes-style inter-sequence SIMD Smith-Waterman). `hyalite` is a Rust reimplementation
//! of Opal and is **not affiliated with or endorsed by** the Opal authors.
//!
//! # Determinism contract
//!
//! This is the crate's primary guarantee, not an implementation detail:
//!
//! > For identical inputs, every backend returns bit-identical results: the same score, the
//! > same database index, the same query end position, and the same target end position. The
//! > selected backend affects performance only, never results.
//!
//! Holding this is why scores use a single, once-defined signed-integer arithmetic model with
//! a documented saturation boundary (see [`ScoreWidth`]), and why tie-breaks are resolved by a
//! scalar argmax over database index rather than a lane-order-dependent horizontal max.
//!
//! The full specification every backend must implement against — the arithmetic model, the
//! score-width proof's coverage of intermediate cells, the tie-break rules, and what is and is
//! not promised — lives in `DETERMINISM.md` at the repository root.
//!
//! # Status
//!
//! Under construction (milestone M0): scalar backend, all four alignment [`Mode`]s, `Score`
//! and `ScoreEnd` [search types](SearchType). SIMD backends, traceback, and the striped
//! `align_pair` path land in later milestones — see `handover.md`.
// `deny` rather than `forbid` so the SIMD backend modules (M2b+) can locally `allow(unsafe_code)`
// for intrinsics; everything else stays unsafe-free.
pub use ;
pub use ;
pub use ;
pub use BestHit;
pub use ;
pub use align_pair;
pub use Mode;
pub use Scoring;
pub use SearchType;
pub use ScoreWidth;