-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Incorrect Result
reference in core::error
.
#134169
Comments
My first though was to simply change the link in |
If that fixes the issue, please feel free to submit a PR |
The specific cause here, by the way, is that #![doc = include_str!("error.md")]
#![stable(feature = "error_in_core", since = "1.81.0")]
use crate::any::TypeId;
use crate::fmt::{Debug, Display, Formatter, Result}; So [ |
Yes, I suspected that was the case. It appears I somehow completely missed that |
Rollup merge of rust-lang#134255 - bjoernager:master, r=Noratrieb Update includes in `/library/core/src/error.rs`. This PR removes the `crate::fmt::Result` include in `/library/core/src/error.rs`. The main issue with this `use` statement is that it shadows the `Result` type from the prelude (i.e. `crate::result::Result`). This indirectly makes all docs references to `Result` in this module point to the wrong type (but only in `core::error` - not `std::error`, wherein this include isn't present to begin with). Fixes: rust-lang#134169
Location
core::error
Summary
The docs for
core::error
contain the following passage:The entry for
Result
links to the docs forcore::fmt::Result
even though it should actually point tocore::result::Result
. The docs forstd::error
, however, do correctly link tostd::result::Result
in this case, despite using the same markup.This issue is present on stable, beta, and nightly branches.
The text was updated successfully, but these errors were encountered: