Rust developers often encounter subtle borrow checker issues that can lead to unsoundness bugs. A static analysis plugin for IDEs like VSCode or IntelliJ could highlight potential problems in real-time.
The plugin would integrate with existing Rust tooling to analyze code patterns that commonly lead to borrow checker violations. It could suggest fixes or workarounds for problematic code segments.
Rust teams in mid-to-large companies would pay for this to prevent costly debugging sessions and improve code quality. The first version could focus on the most common borrow checker pitfalls identified in recent research.
The biggest risk is overlap with existing linters and the Rust compiler's own diagnostics. Differentiation would require deep expertise in Rust's ownership model.