m11-ecosystem

Guidance for selecting, integrating, and managing Rust crates and ecosystem dependencies. ! grep -A 100 '^\[dependencies\]' Cargo.toml 2>/dev/null | head -30 || echo "No Cargo.toml found" Layer 2: Design Choices What's the right crate for this job, and how should it integrate? Before adding dependencies: Before adding a dependency: Is it well-maintained? What's the scope? How does it integrate? To domain constraints (Layer 3): To implementation (Layer 1): - Provides decision tables for common needs (serialization, async runtimes, HTTP, databases, CLI parsing) with recommended crates and evaluation criteria - Covers language interop patterns including C/C++ bindings via bindgen / cbindgen , Python extensions with pyo3 , Node.js addons via napi-rs , and WebAssembly with wasm-bindgen - Includes error code reference (E0433, E0603) with fixes, cargo feature configuration, and workspace management - Offers crate selection criteria (maintenance status, community activity, documentation quality, stability) and anti-patterns to avoid - Is there a standard solution? - What's the maintenance status? - What's the API stability? - Is it well-maintained?