desired: lint to detect uses of int-fallback that flow to foreign varargs
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
See #951.
In particular, from that RFC
unsafe { printf("value: %d\n\0".as_ptr() as *const _, 1); }Note that the numeric argument doesn't have an inferable type and therefore it falls back to the integer-fallback type i32. In C such a literal would have type c_int which coincides with i32 on all supported platforms. However, this might not always be the case.
Therefore, we would like a warn-by-default lint that catches instances of the above.
Contributor guide
No contributing guide indexed for this repository
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 by reading RFC issue #951 and the cited printf example to understand how integer fallback reaches foreign varargs. Define the lint's warning behavior for this pattern and verify that the example is diagnosed without introducing false positives; the payload does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100