-
Notifications
You must be signed in to change notification settings - Fork 13k
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
docs: inline std::ffi::c_str
types to std::ffi
#134791
docs: inline std::ffi::c_str
types to std::ffi
#134791
Conversation
Rustdoc has no way to show that an item is stable, but only at a different path. `std::ffi::c_str::NulError` is not stable, but `std::ffi::NulError` is. To avoid marking these types as unstable when someone just wants to follow a link from `CString`, inline them into their stable paths.
Nominating for beta because the risk is low and the docs are very misleading in their current form. |
Thanks for fixing this. @bors r+ rollup |
@bors r=tgross35 |
Rollup of 8 pull requests Successful merges: - rust-lang#131522 ([macro_metavar_expr_concat] Fix rust-lang#128346) - rust-lang#134379 (Add `into_array` conversion destructors for `Box`, `Rc`, and `Arc`.) - rust-lang#134644 (Document collection `From` and `FromIterator` impls that drop duplicate keys.) - rust-lang#134649 (Fix forgetting to save statx availability on success) - rust-lang#134728 (Use scoped threads in `std::sync::Barrier` examples) - rust-lang#134782 (Update Code Example for `Iterator::rposition`) - rust-lang#134789 (unwinding: bump version to fix naked_asm on Xous) - rust-lang#134791 (docs: inline `std::ffi::c_str` types to `std::ffi`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#134791 - notriddle:notriddle/inline-ffi-error-types, r=tgross35 docs: inline `std::ffi::c_str` types to `std::ffi` Rustdoc has no way to show that an item is stable, but only at a different path. `std::ffi::c_str::NulError` is not stable, but `std::ffi::NulError` is. To avoid marking these types as unstable when someone just wants to follow a link from `CString`, inline them into their stable paths. Fixes rust-lang#134702 r? `@tgross35`
…or-types, r=tgross35 docs: inline `std::ffi::c_str` types to `std::ffi` Rustdoc has no way to show that an item is stable, but only at a different path. `std::ffi::c_str::NulError` is not stable, but `std::ffi::NulError` is. To avoid marking these types as unstable when someone just wants to follow a link from `CString`, inline them into their stable paths. Fixes rust-lang#134702 r? `@tgross35`
Rollup of 8 pull requests Successful merges: - rust-lang#131522 ([macro_metavar_expr_concat] Fix rust-lang#128346) - rust-lang#134379 (Add `into_array` conversion destructors for `Box`, `Rc`, and `Arc`.) - rust-lang#134644 (Document collection `From` and `FromIterator` impls that drop duplicate keys.) - rust-lang#134649 (Fix forgetting to save statx availability on success) - rust-lang#134728 (Use scoped threads in `std::sync::Barrier` examples) - rust-lang#134782 (Update Code Example for `Iterator::rposition`) - rust-lang#134789 (unwinding: bump version to fix naked_asm on Xous) - rust-lang#134791 (docs: inline `std::ffi::c_str` types to `std::ffi`) r? `@ghost` `@rustbot` modify labels: rollup
docs: inline `alloc::ffi::c_str` types to `alloc::ffi` like rust-lang#134791 but for `alloc` r? `@tgross35` `@notriddle`
docs: inline `alloc::ffi::c_str` types to `alloc::ffi` like rust-lang#134791 but for `alloc` r? ``@tgross35`` ``@notriddle``
Rollup merge of rust-lang#134851 - lukas-code:alloc-ffi, r=tgross35 docs: inline `alloc::ffi::c_str` types to `alloc::ffi` like rust-lang#134791 but for `alloc` r? ``@tgross35`` ``@notriddle``
@GuillaumeGomez Should we beta nominate this so that it shows up in the Zulip channel? |
Yes please. Go ahead :) |
How do I do that? Adding the label didn't seem to work. |
Hum weird, normally just putting the label is supposed to do it... |
@Kobzol Did the way to nominate beta backport changed? |
Note that #134851 is also nominated, same change to a different module. |
I just want to double check, @clarfonthey it looks like you marked these |
I don't think so, but I don't actually know how it worked before 🤷 |
Main reason was just that rustdoc always inlines cross-crate exports and I wanted to make it clearer that these are part of the |
[beta] backports - Do not call `extern_crate` on current trait on crate mismatch errors rust-lang#133585 - Correctly handle comments in attributes in doctests source code rust-lang#134260 - Correctly document CTFE behavior of is_null and methods that call is_null. rust-lang#134325 - Make sure we handle `backwards_incompatible_lint` drops appropriately in drop elaboration rust-lang#134486 - Bump compiler `cc` to 1.2.5 rust-lang#134505 - Handle `DropKind::ForLint` in coroutines correctly rust-lang#134575 - docs: inline `std::ffi::c_str` types to `std::ffi` rust-lang#134791 - docs: inline `alloc::ffi::c_str` types to `alloc::ffi` rust-lang#134851 r? cuviper
Rustdoc has no way to show that an item is stable, but only at a different path.
std::ffi::c_str::NulError
is not stable, butstd::ffi::NulError
is.To avoid marking these types as unstable when someone just wants to follow a link from
CString
, inline them into their stable paths.Fixes #134702
r? @tgross35