One related thing: even though the type can be accessed stably, copying the path via the button gives a path that is only usable with unstable e.g. std::ffi::c_str::FromBytesUntilNulError. It may be nice to instead provide the fully stable path for anything that falls into this category (i.e. std::ffi::FromBytesUntilNulError).

For example, #134692 moves Mutex and MutexGuard to a new #[unstable] pub mod std::sync::poison.
They are then reexported with a #[stable] #[doc(inline)] pub use in std::sync.

However, a [`Mutex::lock`] link in the doc for MutexGuard gets resolved as std::sync::poison::Mutex::lock and not std::sync::Mutex::lock (same with try_lock in the screenshot above).

The main ffi module shows the types as re-exported, instead of inlined.

https://doc.rust-lang.org/1.83.0/std/ffi/index.html#reexports

Re-exports

pub use self::c_str::FromBytesUntilNulError;

pub use self::c_str::FromBytesWithNulError;

pub use self::c_str::FromVecWithNulError;

pub use self::c_str::IntoStringError;

pub use self::c_str::NulError;

To fix that, the use statements need marked with #[doc(inline)]. Fixing this, as in returning to the status quo, seems weird. After all, they aren't accessible at the path given.