pub struct UnitView<'a> {
pub statements: &'a [StatementSummary],
pub tokens: &'a [Token],
pub content: FragmentFingerprint,
pub features: &'a UnitFeatures,
pub types: Option<&'a TypeEvidence>,
pub apis: Option<&'a ApiEvidence>,
}Expand description
One unit’s inputs to verification: its flattened statement sequence, the token stream those statements span, and its extracted features.
Fields§
§statements: &'a [StatementSummary]The unit’s statements, flattened in pre-order (see
statement_sequence).
tokens: &'a [Token]The whole token stream of the file the statements came from. A statement span indexes this, so it must be the same stream the summaries were built against.
content: FragmentFingerprintPosition-free content fingerprint of the verified unit. It makes the pair ordering total when feature summaries happen to tie.
features: &'a UnitFeaturesThe unit’s extracted features.
types: Option<&'a TypeEvidence>The types a compiler resolved inside the unit, when one did.
None in the modes that run no compiler, which is a different claim
from empty evidence: absent means nobody looked, and empty means
somebody looked and found nothing to compare.
apis: Option<&'a ApiEvidence>The call targets a compiler resolved inside the unit, when both sides of a comparison can use them. Missing targets deliberately retain the Structural call-name comparison rather than claiming disagreement.