Skip to content
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

Formatting Issue in docs #12736

Closed
sinistersnare opened this issue Mar 6, 2014 · 2 comments · Fixed by #12737
Closed

Formatting Issue in docs #12736

sinistersnare opened this issue Mar 6, 2014 · 2 comments · Fixed by #12737

Comments

@sinistersnare
Copy link
Contributor

Just a quick thing I saw, on the fmt page in the docs here i was looking around, and saw an incorrectly formatted title that looks like this (verbatim): <CODE>WRITE!</CODE>

There is a few more errors like these duplicated under the given example also.

I'm not in a position to clone the repo and fix it, so I just wanted y'all to know. Thanks!

@adrientetar
Copy link
Contributor

cc @alexcrichton

bors added a commit that referenced this issue Mar 6, 2014
Turns out sundown has already escaped this content for us, so there's no need
for us to escape it again.

Closes #12736
@sinistersnare
Copy link
Contributor Author

Thanks! :)

flip1995 pushed a commit to flip1995/rust that referenced this issue May 2, 2024
…licate_errors, r=xFrednet

[`type_complexity`]: Fix duplicate errors

Relates to rust-lang#12379

Following message was duplicated:
```
LL |     fn def_method(&self, p: Vec<Vec<Box<(u32, u32, u32, u32)>>>) {}
   |                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`

error: very complex type used. Consider factoring parts into `type` definitions
  --> tests/ui/type_complexity.rs:55:15
```

Methods `check_trait_item` and `check_fn` were both checking method named def_method.
Now `check_trait_item` only checks methods without body.

---
changelog: [`type_complexity`]: Fix duplicate diagnostics
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants