es:rust

What problem does it solve?

Rust developers need reliable guidance for ownership, borrowing, lifetimes, and ecosystem patterns to avoid subtle correctness and performance issues, and to reduce time lost to borrow-checker and API misdesign.

Core Features & Use Cases

• Ownership, borrowing, and lifetimes mastery: explains move semantics, reference rules, lifetime annotations, and common compiler error patterns so code stays correct as it evolves.
• Idiomatic error handling and control flow: covers Result/Option, ? propagation, and practical choices between thiserror (library) and anyhow (application).
• Async and backend ecosystem patterns: supports task concurrency and shutdown reasoning with Tokio, and gives structured guidance for building web services with Axum/Actix plus database approaches with SQLx/SeaORM.

Example use case: you are implementing an async web endpoint that queries a database and returns structured errors, but you keep hitting lifetime/borrow issues—use this skill to select idiomatic types and fix the architecture before wiring the rest of the stack.

Quick Start

Ask the AI: Write an idiomatic Rust design for an Axum handler that uses SQLx with typed errors, including how to structure ownership across async boundaries and avoid common lifetime and Send issues.