rust-lang / rust-lang/rust-clippy
Thoroughly investigate transmute_undefined_repr
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
See discussion in https://github.com/rust-lang/rust-clippy/pull/8432
The lint is currently in the nursery and has had multiple problems in the past. We should do a deeper investigation: probably running it on a lot of crates and looking for false positives, as well as trying to structure it to be more conservative by default.
Subissues:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion in rust-lang/rust-clippy#8432 and review the transmute_undefined_repr lint's history, including subissue #8501. Investigate its behavior across many crates, record false positives, and define what a more conservative default should mean. Done means the investigation has produced an agreed direction for the lint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100