Tracking Issue for core_ffi_c_extra

Feature gate: #![feature(core_ffi_c_extra)]

This is a tracking issue for providing the aliases for extra C types (c_wchar_t, c_intmax_t, c_iovec,...) via core::ffi. avoid the libc crate to provide better interoperability.
As now libc is looking for release 1.0

Public API

pub use core::ffi::{
    c_intmax_t,
    c_uintmax_t,
    c_wchar_t,
    c_wint_t,
    c_wctype_t,
    c_iovec,
};

After Move IoSlice and IoSliceMut to core::io, core::io::iovec is duplicate of
libc::iovec, we can merge then as core::c_iovec

Maybe there is other libc crate types can moved into core::ffi, we can listing them here.

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

• ACP: rust-lang/libs-team#...
• Implementation: #...
• Final comment period (FCP)^1
• Stabilization PR

Unresolved Questions

• None yet.

Start by reading the core::ffi public API listed in the issue and the referenced core::io::iovec context. The issue names no implementation files or tests, so first determine the relevant core library entry points and any additional libc types that belong in scope. Done requires resolving the API scope and completing the tracking steps through stabilization.