-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Consolidating looping documentation #27305
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
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
I see that Another idea is to put all of the looping ( |
I like this idea a lot. Would you mind updating this PR to do that? |
I've moved all of the looping information to a single page and removed the individual pages for |
@bors: r+ rollup |
📌 Commit 4a5194a has been approved by |
Thanks so much! |
Thank you, it was my pleasure. |
@bors r- This causes tests to fail, http://buildbot.rust-lang.org/builders/auto-mac-32-opt/builds/5983/steps/test/logs/stdio (try it with |
I'm a bit confused. I see from the link that a test failed. But after that it seemed that the merge went through? I'm not sure how to replicate those tests. Looking at the log file I'm not even sure what test failed. Can someone fill me in? |
It didn't merge, the line above is the commit message for the rollup merge being linked to this pull request for mentioning its id (#27305). If it merged this PR would automatically get marked as such 😄 Thsoe are the doctests -- all rust code (except the bits annotated with
It's quite possible that this was a freak error on the buildbot side, in which case we can just retry your pull request. |
(for me when I try |
The hanging is intended. There is an example of an infinite loop: loop {
println!("Loop forever!");
} Shall I annotate it to be ignored? |
⌛ Testing commit a989ed8 with merge 3b1b3f8... |
💔 Test failed - auto-linux-64-nopt-t |
So that failure is reported as:
That seems to relate to the functions.md chapter of the book. My PR doesn't relate to, or touch, that at all. |
@KieranHunt, just FYI, you could use (See https://doc.rust-lang.org/book/documentation.html#running-documentation-tests for all the information.) |
Looks like a spurious error -- stdio disappeared. @bors retry |
I found that the book had little information for `loop`s and `loop` label so I've added some.
I found that the book had little information for
loop
s andloop
label so I've added some.