You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment: rustc 1.31.0-nightly (4bd4e41 2018-10-25) and rustc 1.30.0 (da5f414 2018-10-24)
Rustc produces E0704 error code on the following (syntactically wrong) code:
mod foo {pub(foo)structBar{x:i32}}
error[E0704]: incorrect visibility restriction
--> src/main.rs:35:9
|
35 | pub(foo) struct Bar {
| ^^^ help: make this visible only to module `foo` with `in`: `in foo`
|
= help: some possible visibility restrictions are:
`pub(crate)`: visible only on the current crate
`pub(super)`: visible only in the current module's parent
`pub(in path::to::module)`: visible only on the specified path
error: aborting due to previous error
For more information about this error, try `rustc --explain E0704`.
But but neither rustc --explain E0704 nor https://doc.rust-lang.org/error-index.html is aware of this error
The text was updated successfully, but these errors were encountered:
estebank
added
the
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
label
Oct 26, 2018
@Undin I can pick this up unless you'd want to do it yourself!
@steveklabnik This will be the first the I am writing docs for errors (unless Undin wants to do it of course). I guess the general structure looks a bit like this?:
Added an explanation for the E0704 error.
# Description
Adds an explanation on the E0704 error. I tried to stick as closely to the message that the compiler generates. It's the first time I am fixing error messages here, so if there is something I did wrong or should improve, please let me know.
closesrust-lang#55398
Environment: rustc 1.31.0-nightly (4bd4e41 2018-10-25) and rustc 1.30.0 (da5f414 2018-10-24)
Rustc produces E0704 error code on the following (syntactically wrong) code:
But but neither
rustc --explain E0704
norhttps://doc.rust-lang.org/error-index.html
is aware of this errorThe text was updated successfully, but these errors were encountered: