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

Fix format documentation to mention the Default trait #9808

Closed
orenbenkiki opened this issue Oct 11, 2013 · 1 comment · Fixed by #9938
Closed

Fix format documentation to mention the Default trait #9808

orenbenkiki opened this issue Oct 11, 2013 · 1 comment · Fixed by #9938
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@orenbenkiki
Copy link

The list of "Formatting traits" in libstd/fmt/mod.rs should include the Default trait, even though it is not associated with any format specifier.

@alexcrichton
Copy link
Member

Oh interesting, the Default trait isn't even mentioned at all!

bors added a commit that referenced this issue Oct 19, 2013
flip1995 pushed a commit to flip1995/rust that referenced this issue Dec 17, 2022
…ednet

add `suppress_restriction_lint_in_const` config

According to rust-lang#9808 , add a new lint `suppress_lint_in_const` to report even in const context. BTW, i am not good at naming either, if anyone have a better idea, i am happy to change it.

This PR is still in progress, so i keep it draft.

- \[x] Followed [lint naming conventions][lint_naming]
- \[x] Added passing UI tests (including committed `.stderr` file)
- \[x] `cargo test` passes locally
- \[x] Executed `cargo dev update_lints`
- \[x] Added lint documentation
- \[x] Run `cargo dev fmt`

changelog: Enhancement: [`indexing_slicing`]: add new config `suppress-restriction-lint-in-const` to enable restriction lints, even if the suggestion might not be applicable

r? `@xFrendet`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants