rust-collections

Use the HashMap entry API to update Rust HashMaps without repeated lookups. The entry API provides a canonical pattern for modifying or inserting values in a single pass, eliminating redundant key searches and improving code efficiency.

The best way to handle safe Vec indexing in Rust is using the get method instead of direct indexing. This canonical pattern returns an Option, preventing runtime panics when accessing elements out of bounds.

Avoid taking &Vec or &String as function parameters in Rust because they restrict API flexibility. Using generic slices like &[T] and &str instead is the idiomatic pattern, allowing functions to accept a wider range of types without unnecessary whole-collection cloning.

Plan memory capacity for Rust collections by using the with_capacity constructor before inserting elements. This best practice pre-allocates sufficient memory for Vec and HashMap, preventing frequent reallocations and improving performance during bulk insertions.

Use the entry API for Rust HashMap operations when you need to check if a key exists and then insert or update its value conditionally. This canonical pattern ensures clean, efficient updates without performing multiple separate hash lookups.

Handle UTF-8 strings safely in Rust by following canonical String handling patterns. This ensures proper UTF-8 validation and manipulation, preventing invalid byte sequences and avoiding unnecessary whole-collection cloning.