diff options
| author | Michael Howell <michael@notriddle.com> | 2022-10-04 20:45:13 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-04 20:45:13 -0700 |
| commit | 55ebb61c6826b8f2df1605279c2fdefae2c626d3 (patch) | |
| tree | 83f6cb23e68ccf8831e64d6ff946b3f06fb7d5d4 /compiler/rustc_codegen_gcc | |
| parent | 4025e95113a0fd8ba3ab003796381bc992c27929 (diff) | |
| parent | 5ddaece6508aeb376dc8483fba029f538307536e (diff) | |
| download | rust-55ebb61c6826b8f2df1605279c2fdefae2c626d3.tar.gz rust-55ebb61c6826b8f2df1605279c2fdefae2c626d3.zip | |
Rollup merge of #102650 - Rageking8:slightly-improve-no-return-for-returning-function-error, r=compiler-errors
Slightly improve no return for returning function error Fixes #100607 The rationale is that absolute beginners will be slightly confused as to why certain lines of code in a function does not require a semicolon. (I have actually witness a beginner having this confusion). Hence, a slight rationale is added "to return this value", which signals to the user that after removing said semicolon the value is returned resolving that error. However, if this is not desirable, I welcome any other suggestions. Thanks.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions