diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-01-12 07:12:09 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-12 07:12:09 +0100 |
| commit | b24b0fdcd0e7c1f003a3441bda83c6f9ece17ab8 (patch) | |
| tree | 0d34c5c61888609cca62caf40429b0f6521acb64 /tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.diff | |
| parent | 9ea9e1851d19f86a13659995244c617d6eb5d8bd (diff) | |
| parent | 2b70a3df7a73b283e7f19439a98c81bb66f6a852 (diff) | |
| download | rust-b24b0fdcd0e7c1f003a3441bda83c6f9ece17ab8.tar.gz rust-b24b0fdcd0e7c1f003a3441bda83c6f9ece17ab8.zip | |
Rollup merge of #92699 - camelid:private-fields, r=jsha
rustdoc: Display "private fields" instead of "fields omitted"
Also:
* Always use `/* */` block comments
* Use the same message everywhere, rather than sometimes prefixing
with "some"
When I first read rustdoc docs, I was confused why the fields were being
omitted. It was only later that I realized it was because they were
private. It's also always bothered me that rustdoc sometimes uses `//`
and sometimes uses `/*` comments for these messages, so this change
makes them all use `/*`.
Technically, I think fields can be omitted if they are public but
`doc(hidden)` too, but `doc(hidden)` is analogous to privacy. It's
really just used to emulate "doc privacy" when -- because of technical
limitations -- an item has to be public. So I think it's fine to include
this under the category of "private fields".
r? ```@jsha```
Diffstat (limited to 'tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.diff')
0 files changed, 0 insertions, 0 deletions
