Should tag wikis contain frequently suggested style points?

Question

Over in rust, there are a set of style points that come up in almost every review of substance. I've found myself becoming more and more terse when raising those issues, which is ultimately a detriment to the people that are here looking for useful feedback.

I had the idea of adding some generally-accepted improvements, along with explanations and hopefully links to more official sources, to the tag wiki. These could be longer form, and answerers could link to them instead of re-explaining each time.

Rust also has some prominent tools that perform automatic formatting and linting. These tools tend to have documented rationale, and it would be great if people had the chance to know about them and run them. I figured I could add links to those as well.

Other languages also have official or semi-official guides. For example, Python has PEP8, Ruby has Rubocop, there are multiple style guides for Java and C++, etc.

When I went to edit the tag wiki, I found a bunch of introductory text that explains what Rust is. I think that at the point that someone is asking for a review of Rust code, they already know all that.

I found Would it make sense to copy (some) tag wikis from SO?, which seems to promote the process of copying tag wikis from Stack Overflow. Stack Overflow wikis are aimed at providing a high-level overview of the tag, but that doesn't seem useful here on Code Review. The top answer for 'Canonical' questions to help address common issues indicates that the tag wiki should be used as an entry point to frequent issues.

I believe there are two tightly-related aspects to this question:

1. Should we put common style points relevant to a tag in the tag wiki?
2. Should we remove/reduce aspects of the tag wiki that don't have to do specifically with code review?

Answer 1

Yes, it would be a good idea to mention common code review issues in tag wikis.

I've done this, for example, with collatz-sequence:

These sequences are sometimes called "hailstone sequences" because they can cycle between small and sometimes surprisingly large values before eventually arriving at 1. For example, the Collatz sequence for \$n = 159487\$ contains a number exceeding \$2^{31}\$, and would overflow a signed 32-bit integer type.

Please stick to objective non-controversial advice, such as official style guides.

Unfortunately, tag wiki texts are not easy to get to in the Stack Exchange UI, so they probably won't be discovered by most users spontaneously.

---

Unlike Stack Overflow, we currently don't have a large army of high-rep users to maintain the tag wikis, so I do tend to omit information that will easily become outdated.