Rust for C-Programmers

16.7 Best Practices for Type Conversions

Effective and safe type conversion relies on choosing the right tool and understanding its implications:

1. Prioritize Correct Types: Design data structures using the most appropriate types initially to minimize the need for conversions later.
2. Prefer From/Into for Infallible Conversions: Use these traits for conversions guaranteed to succeed. They clearly communicate intent, are idiomatic, and leverage the type system effectively.
3. Mandate TryFrom/TryInto for Fallible Conversions: When a conversion might fail (e.g., narrowing numeric types, parsing, validation), use these traits. They enforce explicit error handling via Result, making code robust.
4. Use as Cautiously: Reserve as for simple, well-understood primitive numeric casts where truncation/saturation/precision loss is acceptable by design, or for essential low-level pointer/integer casts within unsafe blocks. Avoid as for potentially failing numeric conversions where errors should be handled.
5. Avoid transmute Unless Absolutely Necessary: transmute subverts type safety. Exhaust safer alternatives (to/from_bytes, pointer casts, unions, From/TryFrom) first. If transmute is required, isolate it in minimal unsafe blocks, rigorously document the safety invariants, and consider alternatives carefully.
6. Implement Display/FromStr for Text Representations: Use these standard traits for converting your custom types to and from user-readable strings.
7. Utilize cargo clippy: Regularly run cargo clippy. It includes lints that detect many common conversion pitfalls, such as potentially lossy casts, unnecessary casts, integer overflows, and suggests using TryFrom over as where appropriate.