Apply the #[async_trait] macro to enable async methods on Rust trait objects.
npx skills add https://github.com/yankeeinlondon/rusty-biscuit --skill async-trait
Please help me install this Agent Skill. Skill: async-trait Source: https://github.com/yankeeinlondon/rusty-biscuit/tree/main/.claude/skills/async-trait Command: npx skills add https://github.com/yankeeinlondon/rusty-biscuit --skill async-trait
Using async functions in trait objects is not natively supported in stable Rust. This skill explains how the #[async_trait] macro enables object-safe async methods, including Send/Sync bounds and performance implications.
Annotate a trait and its impl with #[async_trait] and start calling async methods on trait objects.
High-intent search queries and answers about installing and using this skill.
Using async functions in trait objects requires the #[async_trait] macro applied to both trait definitions and implementations, which makes async methods object-safe for dynamic dispatch across plugin systems and dependency injection patterns.
Stable Rust lacks native async trait object support because async methods return compiler-inferred futures. The #[async_trait] macro resolves this by boxing the returned future and applying default Send + Sync bounds for safe dynamic dispatch.
Handling Send bounds for async trait objects is managed by the #[async_trait] macro, which enforces default Send + Sync bounds on futures while supporting an optional !Send variant for single-threaded execution contexts.
Performance implications of async traits with dynamic dispatch include boxing overhead for returned futures and vtable lookup costs. The macro documents expansion details and compares dispatch approaches to help evaluate these trade-offs.
Async traits are fully usable for plugin registries and dependency injection in Rust. The #[async_trait] macro provides practical usage patterns specifically designed for registries, plugins, and dependency injection requiring dynamic dispatch of async interfaces.
Avoid the async-trait macro when boxing overhead from dynamic dispatch is unacceptable for your performance requirements, or when static dispatch via generic async functions suffices without needing object-safe trait objects.
CallMeLuigiv2Implement Tokio-based async patterns for concurrent Rust tasks.
CallMeLuigiv2Evaluate Rust polymorphism decisions between generics and trait objects.
SuperlendClarify underspecified requirements by asking 1-5 essential questions before execution.
adelabdelgawadDesign reusable Rust abstractions using traits, generics, and static dispatch.
