diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2020-01-04 02:19:54 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-01-04 02:19:54 +0100 |
| commit | 689e29f0f58641d4c4532463b13af7c656ae84b8 (patch) | |
| tree | b7be4867fc9223206c5b3a4798376e25cbe4251e /src/test/ui/const-generics/array-size-in-generic-struct-param.rs | |
| parent | b32dc91372abf7a9b86a8cddbe490e500aa63969 (diff) | |
| parent | 7fd014d56986d7b52c49f07fb8db9529059d839d (diff) | |
| download | rust-689e29f0f58641d4c4532463b13af7c656ae84b8.tar.gz rust-689e29f0f58641d4c4532463b13af7c656ae84b8.zip | |
Rollup merge of #67835 - euclio:delimiter-wording, r=Centril
tweak wording of mismatched delimiter errors This PR improves the wording of the "incorrect delimiter" error messages. Here's a quick rationale: - *"un-closed" -> "unclosed"*: "unclosed" is valid English, so there's no need to hyphenate the prefix. This should be pretty uncontroversial, I think. - *"close delimiter" -> "closing delimiter"*: In my anecdotal experience, I've always heard "closing delimiter" or "closing parenthesis". In addition, the codebase already uses this terminology in comments and function names more than "close delimiter", which could indicate that it's more intuitive. - "incorrect delimiter" -> "mismatched delimiter": "Incorrect delimiter" is vague; why is it incorrect? "mismatched" clearly indicates why the delimiter is causing the error. r? @estebank
Diffstat (limited to 'src/test/ui/const-generics/array-size-in-generic-struct-param.rs')
0 files changed, 0 insertions, 0 deletions