How does this skill help with Rust E0277 errors?

It analyzes why a type fails Send or Sync bounds and suggests structural changes, such as using Arc for sharing or switching to message passing, rather than just suggesting quick fixes.

Can it help me choose between threads and async?

Yes, it provides a decision flowchart to determine if your task is CPU-bound (parallelism via threads/rayon) or I/O-bound (concurrency via tokio/async-std).

How does it handle async-specific deadlocks?

The skill identifies anti-patterns like holding a MutexGuard across an .await point and suggests scoping guards or using async-aware locks to prevent runtime hangs.

Does it support specific web frameworks like Axum or Actix?

Yes, it includes 'Trace Up' logic to detect if you are working within a web context, ensuring that shared state complies with the specific thread-safety requirements of those frameworks.

Rust Concurrency & Async Expert

Name: Rust Concurrency & Async Expert
Author: actionbook

byactionbook

•

596

Developer Tools

Optimizes Rust concurrency and asynchronous code by resolving Send/Sync errors and implementing thread-safe architectural patterns.

About

The m07-concurrency skill provides deep domain expertise for Rust developers navigating the complexities of multi-threaded and asynchronous programming. It helps identify whether a workload is CPU-bound or I/O-bound, guides the selection of appropriate primitives like Arc, Mutex, or channels, and troubleshoots common compiler errors such as E0277. By utilizing a 'Trace Up' methodology, the skill ensures that concurrency fixes align with higher-level domain constraints in web, cloud-native, or financial applications while preventing common pitfalls like deadlocks and MutexGuard leakage across await points.

Key Features

Implements efficient shared mutable state patterns using Arc, Mutex, and RwLock
Identifies and prevents deadlocks and thread-safety anti-patterns
Optimizes async performance by auditing blocking calls and lock holding durations
Provides workload-specific guidance for choosing between rayon and tokio
596 GitHub stars
Resolves E0277 Send and Sync trait violations with architectural fixes

Use Cases

Parallelizing CPU-intensive tasks using rayon or std::thread
Debugging 'Future is not Send' errors in high-concurrency web API handlers
Designing thread-safe state management for microservices and cloud-native apps

About

Key Features

Implements efficient shared mutable state patterns using Arc, Mutex, and RwLock
Identifies and prevents deadlocks and thread-safety anti-patterns
Optimizes async performance by auditing blocking calls and lock holding durations
Provides workload-specific guidance for choosing between rayon and tokio
596 GitHub stars
Resolves E0277 Send and Sync trait violations with architectural fixes

Use Cases

Parallelizing CPU-intensive tasks using rayon or std::thread
Debugging 'Future is not Send' errors in high-concurrency web API handlers
Designing thread-safe state management for microservices and cloud-native apps