-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-export core::ffi::FromBytesUntilNulError in std::ffi #113701
Conversation
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: rust-lang#95027
(rustbot has picked a reviewer for you, use r? to override) |
Since this probably should have been included as part of @rustbot label +T-libs-api -T-libs (not sure if it will let me do this one) r? libs-api |
@rust-lang/libs-api: Relevant to the "multiple feature gates per API" idea we talked about a few months back. CStr in core (tracking issue: #98314) and CStr::from_bytes_until_nul (tracking issue: #95027) were unstable concurrently, and this causes us to lose track of things. In this case it was luckily in the missing-API way and not in the accidentally-stable way. This PR re-exports core::ffi::FromBytesUntilNulError (the error type of CStr::from_bytes_until_nul) as std::ffi::FromBytesUntilNulError, matching how CStr and FromBytesWithNulError have already been re-exported from core::ffi to std::ffi for a while. @rfcbot fcp merge |
Team member @dtolnay has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
I think |
If it becomes an issue then you can just make up a new feature name. |
Yes, changing the line to Also thanks, this is my first library contribution so I appreciate the heads up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@bors r+ |
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#109318 (Make `Debug` representations of `[Lazy, Once]*[Cell, Lock]` consistent with `Mutex` and `RwLock`) - rust-lang#113701 (Re-export core::ffi::FromBytesUntilNulError in std::ffi) - rust-lang#113804 (Resolve correct archive version name in `opt-dist`) - rust-lang#114165 (Add missing rvalues to smir) - rust-lang#114182 (clean up after 113312) - rust-lang#114193 (Update lexer emoji diagnostics to Unicode 15.0) - rust-lang#114200 (Detect trait upcasting through struct tail unsizing in new solver select) r? `@ghost` `@rustbot` modify labels: rollup
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