rust/tests/ui/extern/extern-C-non-FFI-safe-arg-ice-52334.stderr

warning: `extern` fn uses type `CStr`, which is not FFI-safe
  --> $DIR/extern-C-non-FFI-safe-arg-ice-52334.rs:7:12
   |
LL | type Foo = extern "C" fn(::std::ffi::CStr);
   |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not FFI-safe
   |
   = help: consider passing a `*const std::ffi::c_char` instead, and use `CStr::as_ptr()`
   = note: `CStr`/`CString` do not have a guaranteed layout
   = note: `#[warn(improper_ctypes_definitions)]` on by default

warning: `extern` block uses type `CStr`, which is not FFI-safe
  --> $DIR/extern-C-non-FFI-safe-arg-ice-52334.rs:10:18
   |
LL |     fn meh(blah: Foo);
   |                  ^^^ not FFI-safe
   |
   = help: consider passing a `*const std::ffi::c_char` instead, and use `CStr::as_ptr()`
   = note: `CStr`/`CString` do not have a guaranteed layout
   = note: `#[warn(improper_ctypes)]` on by default

warning: 2 warnings emitted
Add a special case for CStr/CString in the improper_ctypes lint Instead of saying to "consider adding a `#[repr(C)]` or `#[repr(transparent)]` attribute to this struct", we now tell users to "Use `*const ffi::c_char` instead, and pass the value from `CStr::as_ptr()`" when the type involved is a `CStr` or a `CString`. Co-authored-by: Jieyou Xu <jieyouxu@outlook.com> 2024-03-23 09:49:05 -05:00			warning: `extern` fn uses type `CStr`, which is not FFI-safe
add issue numbers via // issue: rust-lang/rust#ISSUE_NUM directive 2024-03-22 13:21:50 -05:00			`--> $DIR/extern-C-non-FFI-safe-arg-ice-52334.rs:7:12`
add test for #52334 Fixes #52334 2024-03-22 11:49:04 -05:00			`\|`
			`LL \| type Foo = extern "C" fn(::std::ffi::CStr);`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not FFI-safe`
			`\|`
Add a special case for CStr/CString in the improper_ctypes lint Instead of saying to "consider adding a `#[repr(C)]` or `#[repr(transparent)]` attribute to this struct", we now tell users to "Use `*const ffi::c_char` instead, and pass the value from `CStr::as_ptr()`" when the type involved is a `CStr` or a `CString`. Co-authored-by: Jieyou Xu <jieyouxu@outlook.com> 2024-03-23 09:49:05 -05:00			= help: consider passing a `*const std::ffi::c_char` instead, and use `CStr::as_ptr()`
			= note: `CStr`/`CString` do not have a guaranteed layout
add test for #52334 Fixes #52334 2024-03-22 11:49:04 -05:00			= note: `#[warn(improper_ctypes_definitions)]` on by default

Add a special case for CStr/CString in the improper_ctypes lint Instead of saying to "consider adding a `#[repr(C)]` or `#[repr(transparent)]` attribute to this struct", we now tell users to "Use `*const ffi::c_char` instead, and pass the value from `CStr::as_ptr()`" when the type involved is a `CStr` or a `CString`. Co-authored-by: Jieyou Xu <jieyouxu@outlook.com> 2024-03-23 09:49:05 -05:00			warning: `extern` block uses type `CStr`, which is not FFI-safe
add issue numbers via // issue: rust-lang/rust#ISSUE_NUM directive 2024-03-22 13:21:50 -05:00			`--> $DIR/extern-C-non-FFI-safe-arg-ice-52334.rs:10:18`
add test for #52334 Fixes #52334 2024-03-22 11:49:04 -05:00			`\|`
			`LL \| fn meh(blah: Foo);`
			`\| ^^^ not FFI-safe`
			`\|`
Add a special case for CStr/CString in the improper_ctypes lint Instead of saying to "consider adding a `#[repr(C)]` or `#[repr(transparent)]` attribute to this struct", we now tell users to "Use `*const ffi::c_char` instead, and pass the value from `CStr::as_ptr()`" when the type involved is a `CStr` or a `CString`. Co-authored-by: Jieyou Xu <jieyouxu@outlook.com> 2024-03-23 09:49:05 -05:00			= help: consider passing a `*const std::ffi::c_char` instead, and use `CStr::as_ptr()`
			= note: `CStr`/`CString` do not have a guaranteed layout
add test for #52334 Fixes #52334 2024-03-22 11:49:04 -05:00			= note: `#[warn(improper_ctypes)]` on by default

			`warning: 2 warnings emitted`