sage-sanity-check

To check Rust code for non-exhaustive matches, run a sanity check to identify SAGE-specific anti-patterns. The tool scans modified code to detect inference variables on type errors and error type constructions lacking diagnostics, ensuring code integrity.

SAGE-specific anti-patterns in Rust code include non-exhaustive matches, inference variables appearing on type errors, and constructing error types without associated diagnostics. Identifying these patterns maintains code quality and prevents subtle issues.

To run a sanity check on modified Rust code, invoke the tool with a description of your changes and the instructions file. It analyzes the code and reports any detected SAGE-specific anti-patterns, ensuring modifications meet quality standards.

This anti-pattern detection tool is specifically intended for code quality assurance within the SAGE codebase. While it identifies standard Rust issues like non-exhaustive matches, its checks for error type constructions are tailored to SAGE-specific standards.

Rust error type construction lacks diagnostics when developers bypass standard error reporting practices. The sanity check identifies this anti-pattern, flagging error constructions that fail to provide diagnostic information to help debug type errors.