maverick-rust-async
Rust async/await with Tokio and async patterns
When & Why to Use This Skill
This Claude skill provides expert-level assistance for Rust asynchronous programming, specifically focusing on the Tokio runtime and async/await patterns. It helps developers identify critical concurrency issues, such as blocking calls in async contexts, ensures thread safety through Send/Sync trait validation, and promotes best practices for task spawning and Future management to build high-performance, reliable systems.
Use Cases
- Detecting and resolving 'CRITICAL' blocking operations within async functions that could stall the Tokio executor.
- Auditing thread-safety by identifying improper use of non-Send types like 'Rc' in multi-threaded async environments.
- Optimizing resource management and task lifecycles using JoinHandle, Arc, and async move patterns.
- Providing architectural guidance on implementing complex asynchronous workflows and ensuring proper Pinning of Futures.
| name | maverick-rust-async |
|---|---|
| description | Rust async/await with Tokio and async patterns |
| version | 1.0.0 |
Rust Async Skill
Tokio Basics
#[tokio::main]
async fn main() {
let result = fetch_data().await;
}
async fn fetch_data() -> Result<String, Error> {
// async operation
}
Spawning Tasks
let handle = tokio::spawn(async move {
expensive_operation().await
});
let result = handle.await?;
Send + Sync Bounds
Send: Can transfer across thread boundariesSync: Can be shared across threads (&T is Send)- Use
Arcinstead ofRcfor thread-safe reference counting
Review Severity
- CRITICAL: Blocking calls in async functions
- MAJOR: Using Rc in async code (not Send)
- MINOR: Not using async context managers