-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rewrite E0158
error-code docs for clarity
#105744
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Nilstrieb (or someone else) soon. Please see the contribution instructions for more information. |
Please fix the CI error and squash your commits then I'll approve it. Thanks for working on this! |
Done, hopefully should be alright. Thanks for all your help. |
328dee0
to
fded03e
Compare
@GuillaumeGomez I also have new long-form error docs for E0320 and E0472, should I mark them for you to review? (I haven't PRed them yet) |
Sure. I'm currently in holiday so if the current pace is fine for you, feel free to assign them to me. |
Thanks! @bors r+ rollup |
…iaskrgr Rollup of 8 pull requests Successful merges: - rust-lang#105725 (Allow `impl ~const Trait` opaque types) - rust-lang#105744 (Rewrite `E0158` error-code docs for clarity) - rust-lang#105747 (Fix ICE calling method on auto trait) - rust-lang#105748 (doc: Fix a few small issues) - rust-lang#105756 (rustdoc: simplify CSS for codeblock tooltips) - rust-lang#105757 (rustdoc: remove unused CSS `.sub-settings`) - rust-lang#105764 (rustdoc: name the source page sidebar-toggle `#src-sidebar-toggle`) - rust-lang#105774 (Remove unused stderr files) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Fixes #105585.
The
E0158
error-code docs are unclear. It doesn't explain all three different variants of the error and doesn't explain why the error occurs. This PR cleans it up a bit and brings it properly into line with RFC1567.I'm a first time Rust contributor so I've probably not got it quite right. I also haven't run the whole build process because I assume that my minor docs changes shouldn't break everything.