Lint to warn about str::as_ptr() usage in ffi call · rust-lang/rust-clippy#1236

(0 comments) (0 reactions) (0 assignees)Rust (10,406 stars) (1,391 forks)batch import

A-lintL-correctnessT-middlegood first issue

説明

Hello. It would be nice to have a warning when using str::as_ptr() in a ffi call instead of using CStr.

For instance, in the following code:

unsafe { printf("Hello".as_ptr() as *const _) };

should give a warning and propose something like:

let cstring = CString::new("Hello".as_bytes()).unwrap();
unsafe { printf(cstring.as_ptr()) };

Thanks to add this lint.

技術スタック: rust
領域: developer experiencetooling
Issue 種別: feature
難度: 3
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: familiarity with Rust FFIclippy lint creation basicsunderstanding of CStr
初心者向け度: 60
調査方針: Examine existing clippy lints that target function calls (e.g., the 'fn to numeric cast' lint) to understand the pattern matching on function arguments. Follow the clippy development guide at https://github.com/rust lang/rust clippy/blob/master/CONTRIBUTING.md to set up the environment and add a new lint. The lint should detect calls to `str::as ptr()` where the result is passed to an extern function; consider using `fn has item` or checking the function call's parameter types.