-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Remove misleading code example from The Guide #15899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I think the reader will not even notice we have skipped a piece of text. |
Eh, I think it's a useful thing to point out. It's contrasting variable assignment with a |
I think that is a valid alternative. However, at this point in the guide the EDIT: even if you do this, |
@aochagavia I think the point is to contrast a |
I am super torn. @kballard nails it: it's to contrast that So: can we accomplish this goal through some other example? Is there a time when |
How about something like this:
No code example necessary. This explanation is largely just to avoid confusion in readers who read the info on |
I like it! Do you have any improvements on that @steveklabnik? EDIT: maybe we can replace "RHS" for something more accessible for beginners. |
Yes, with the expansion of "right hand side," I think that's fine. |
I have committed a slightly modified version. Please tell me if you think something needs to be changed. |
Actually I think "assigned value" instead of "right hand side" may be simpler. |
I think you are right, check out the new version. |
The removed code caused confusion because it is not clear that the type of `y` is actually `()`
Nice. |
The removed code caused confusion because it is not clear that the type of `y` is actually `()`
internal: Sync from rust
The removed code caused confusion because it is not clear that the type of
y
is actually()