Rust Ecosystem

Selection Policy

Prefer the standard library when sufficient. Then inspect platform facilities and suitable approved workspace dependencies. For commodity functionality not adequately covered, evaluate mature ecosystem crates before writing a custom implementation. Not having a dependency installed is not a reason by itself to handroll it.

These are project preferences and starting points, not universal Rust mandates or a starter dependency checklist. Do not add unused crates or parallel libraries for the same responsibility. Consider maintenance, licensing, security, minimum Rust version, target support, no_std, features, native build requirements, and footprint. Check current documentation and repository constraints instead of assuming a listed crate/version is always appropriate.