Rust Performance and Layout

Use this when performance matters enough to justify design pressure.

Working stance

• Measure before changing shapes.
• Fix the largest hot-path cost, not the most obvious micro-optimization.
• Keep iterator pipelines lazy until you genuinely need a collection.
• Reuse allocations and tighten data movement before reaching for cleverness.
• Keep layout decisions explicit when they affect cache use or FFI.
• Prefer simple code unless profiling proves it is the bottleneck.

Decision surface