diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2023-02-21 14:20:00 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-21 14:20:00 +0530 |
| commit | 7dcf7fe737e90ccec46864333c1bb0f43ed1a258 (patch) | |
| tree | 264b8bc1155dd2a2701eb7ec841f3b86745ce9a7 | |
| parent | 076e6270232ef22ff9b26e2a3c9c3f19e960eb5e (diff) | |
| parent | 18f5f0c4737e277fcab292363bebb7866430d90d (diff) | |
| download | rust-7dcf7fe737e90ccec46864333c1bb0f43ed1a258.tar.gz rust-7dcf7fe737e90ccec46864333c1bb0f43ed1a258.zip | |
Rollup merge of #108272 - MrNossiom:master, r=thomcc
docs: wrong naming convention in struct keyword doc Noticed that the naming convention mentioned is not the right one. As far as I know, PacalCase is the naming convention used for structs names. PacalCase is not the same as camelCase
| -rw-r--r-- | library/std/src/keyword_docs.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/library/std/src/keyword_docs.rs b/library/std/src/keyword_docs.rs index e35145c4ade..203c490fa29 100644 --- a/library/std/src/keyword_docs.rs +++ b/library/std/src/keyword_docs.rs @@ -1568,7 +1568,7 @@ mod static_keyword {} /// /// # Style conventions /// -/// Structs are always written in CamelCase, with few exceptions. While the trailing comma on a +/// Structs are always written in UpperCamelCase, with few exceptions. While the trailing comma on a /// struct's list of fields can be omitted, it's usually kept for convenience in adding and /// removing fields down the line. /// |