Module flycheck 

The rustc flycheck: on save, compile the document through the AOT backend’s mapped codegen and run cargo check over it, translating every finding back to English with real user-source spans — the borrow checker, speaking LOGOS.

Never on the interactive path: saves trigger it, a per-document generation guard drops stale results (a newer save always wins), edits clear findings outright (their positions would lie), and a machine without cargo degrades to interactive-only diagnostics.

Structs

CargoFlycheck

Shells out to cargo check through [logicaffeine_compile::compile::rustc_check], one persistent cache directory per workspace (warm incremental runs), single-flight per workspace so two saves never race one cargo target dir.

Flycheck

Per-document flycheck state: save generations and the last published findings (already converted to diagnostics against the checked text).

FlycheckFinding

One translated rustc finding.

Constants

FLYCHECK_SOURCE

The diagnostic source label — distinct from interactive logicaffeine diagnostics so editors and users can tell the two engines apart.

Traits

FlycheckRunner

The check engine seam. The real runner shells out to cargo; tests inject mocks so the server’s merge/staleness/dedup behavior is provable without a toolchain.