Skip to content

docs(ch03-03): clarify statement evaluates to unit type (#4678)#4779

Open
Dodothereal wants to merge 1 commit into
rust-lang:mainfrom
Dodothereal:fix/issue-4678-statement-vs-unit-type
Open

docs(ch03-03): clarify statement evaluates to unit type (#4678)#4779
Dodothereal wants to merge 1 commit into
rust-lang:mainfrom
Dodothereal:fix/issue-4678-statement-vs-unit-type

Conversation

@Dodothereal

Copy link
Copy Markdown

Fixes #4678

Summary

Chapter 3.3 says 'statements don't evaluate to a value, which is
expressed by (), the unit type. Therefore, nothing is returned'.
That wording implicitly names () then says 'nothing is returned',
contradicting the immediately preceding clause. Reword to one
unbroken sentence: statements evaluate to () which doesn't satisfy
the declared i32 return type.

The compiler error and the suggestion (remove the semicolon) remain
correct and unchanged.

Test plan

  • git diff: single file, 5 insertions, 5 deletions.

AI assistance

Prepared with help from an AI coding assistant; reviewed end-to-end.

Fixes rust-lang#4678: the previous wording 'statements don't evaluate to a
value' followed by 'Therefore, nothing is returned' internally
contradicts the immediately preceding clause that names '()', the
unit type, as the type produced. Rewrite the sentence to a single
thread that says statements evaluate to () which doesn't satisfy the
declared i32 return type.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"nothing is returned" contradicts compiler output in Functions chapter

1 participant