fast-rust
Concise guidance for high-quality Rust engineering, balancing correctness, maintainability, and performance.
Purpose and Triggers
- Writing new code, refactoring, reviewing, or designing public APIs/CLIs.
- Rust or files with
.rs. - Prefer clear boundaries, error semantics, and evolvability.
Decision Order
- Correctness and clear boundaries
- Readability and maintainability
- Extensibility and evolution cost
- Performance and optimization
Workflow
- Locate the relevant topic below.
- Apply the guidance and examples.
- Read the reference if you need more detail.
Topics
| Topic | Guidance | Reference |
|---|---|---|
| Error Design | Design error boundaries and semantics before propagation | references/error-design.md |
| Compilation | Optimize build time and release performance with measured changes | references/compilation-optimization.md |
| Type Exercise | Type-level exercise for expression engines and dispatch | references/type-exercise.md |
References
- Each topic file lists source URLs in frontmatter
urls.