diff options
| author | Allen Wild <allenwild93@gmail.com> | 2023-07-14 11:08:57 -0400 |
|---|---|---|
| committer | Allen Wild <allenwild93@gmail.com> | 2023-07-14 11:08:57 -0400 |
| commit | fda3d2abaa325c49a6ff382a624af59c6e75db37 (patch) | |
| tree | 3f7c311ef62aa10644fee763b3cd8fc2ceda81a4 | |
| parent | df5c2cf9bc60fa935aef31a217d9fa0a328d7fe2 (diff) | |
| download | rust-fda3d2abaa325c49a6ff382a624af59c6e75db37.tar.gz rust-fda3d2abaa325c49a6ff382a624af59c6e75db37.zip | |
Re-export core::ffi::FromBytesUntilNulError in std::ffi
Like the other CStr and CString error types, make a re-export for std::ffi::FromBytesUntilNulError. This seems to have slipped through the cracks in the cstr_from_bytes_until_nul implementation and core_c_str migration. Tracking Issue: #95027
| -rw-r--r-- | library/std/src/ffi/mod.rs | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/library/std/src/ffi/mod.rs b/library/std/src/ffi/mod.rs index 3ddb8748753..b0484474712 100644 --- a/library/std/src/ffi/mod.rs +++ b/library/std/src/ffi/mod.rs @@ -156,6 +156,8 @@ #[stable(feature = "alloc_c_string", since = "1.64.0")] pub use alloc::ffi::{CString, FromVecWithNulError, IntoStringError, NulError}; +#[stable(feature = "cstr_from_bytes_until_nul", since = "CURRENT_RUSTC_VERSION")] +pub use core::ffi::FromBytesUntilNulError; #[stable(feature = "core_c_str", since = "1.64.0")] pub use core::ffi::{CStr, FromBytesWithNulError}; |