Explain in M-STATIC-VERIFICATION general motivation for custom lints we picked & expand

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
documentation, tooling

Research direction

Start at the M-STATIC-VERIFICATION section and inspect the Rust lint configuration to find where custom lints are documented and where redundant_pub_crate can be allowed. Done means the motivation is expanded, the requested lint setting is added, and the statistics TODO is resolved or clearly scoped.

Written by the indexing model from the issue text.

Description

easy-pr issue

Add a few more words that they make code look nicer, etc.

Also add redundant_pub_crate = "allow".

TODO: Any statistics which lints are usually enable / suppressed in ecosystem? IIRC there was an experiment about that a few years ago, but can't find it anymore.

Dominant language
Rust
Stars
200
Forks
25
Avg merge
3m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/rust-guidelines

All issues in microsoft/rust-guidelines

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.