rust-async-await-module-patterns

You structure Rust async/await module patterns by separating sync, async, and bridge logic into a recommended directory structure, which prevents runtime conflicts and ensures code maintainability. This approach keeps asynchronous operations isolated and organized.

To ensure Send + Sync compliance for Rust types exposed through FFI, you must follow specific safety guidelines that allow asynchronous types to safely cross foreign function interface boundaries. This Skill details those FFI safety practices to prevent data races.

The best way to share a single Tokio runtime instance is through efficient runtime management patterns that avoid creating multiple runtimes. This Skill demonstrates how to manage and share the Tokio runtime safely within high-performance Rust libraries.

Yes, you can use these Rust async/await patterns to interact with synchronous codebases like Python or Ruby. The module organization guidelines help manage asynchronous operations safely and efficiently when bridging sync and async environments.

Common anti-patterns in asynchronous Rust applications include improper runtime sharing and unsafe FFI boundaries. This Skill identifies these anti-patterns and provides testing strategies to validate your async Rust application structure.