analysis-incomplete
Default severity: warning · Identifier: weavec::analysis-incomplete
What it means
Section titled “What it means”An operation could not be modeled completely (RFC 0014). Message: analysis is incomplete: <reason>. Reasons identify unsupported copies of pointer-containing storage, incompatible or unknown object views, unavailable callback contexts, and exhausted function or summary iterations. RFC 0015 adds unresolved array selections/updates, incomplete symbolic composition, unavailable source snapshots, uncertain range membership and element/range limits. RFC 0016 adds unresolved call alias relationship, unrepresentable call context input path, call context input path limit reached, call context relationship limit reached, and call context unavailable or limit reached. RFC 0017 adds unsupported numeric widths, expressions, conditions, outputs and extent projections; examples include unsupported integer width greater than 64 bits, unsupported numeric output projection, unsupported numeric condition projection, unsupported extent requirement condition and unrepresentable variable array byte extent. A represented symbolic array copy can join copied and untouched contents without warning solely because membership is undecided. Known effects still apply; this warning describes missing coverage, rather than proving that the operation itself is invalid.
How to resolve it
Section titled “How to resolve it”Read the reason to identify the unsupported operation or exhausted analysis bound. Simplify the affected operation, expose a supported interface, or consult the coverage and validation records. Ordinary analysis may continue, but an absence of further diagnostics is not a proof of safety.