Rules for numeric type conversions in Luma. Use when writing or reviewing code that casts between integer or float types, especially across different widths.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Always use From/Into, never as:
// Correct
let x: u64 = u64::from(byte);
let x: u64 = byte.into();
// Wrong — triggers clippy::cast_lossless
let x = byte as u64;
clippy::cast_lossless enforces this automatically.
Only use as when the bound is provably safe and documented:
// Acceptable — bound is clear from context
let idx = offset as usize; // offset is always < usize::MAX by construction
// Preferred when bound is not obvious
let idx = usize::try_from(offset).expect("offset fits usize");
If overflow is possible and silent truncation is wrong, use try_from and handle the error explicitly.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guidelines for writing platform-specific code in Luma. Use when adding or modifying code that behaves differently on Unix vs Windows, including shell commands, file paths, process spawning, or platform-specific tests.
The English summary is being prepared. Showing the original description.
Workflow for creating, updating, or superseding RFCs in Luma. Use when the task involves opening a new RFC, updating RFC status, marking an RFC as superseded or implemented, or deciding whether a change needs an RFC at all.
The English summary is being prepared. Showing the original description.