-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 13 pull requests #31359
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
Rollup of 13 pull requests #31359
Conversation
The doc part of rust-lang#30459
E0507 can occur when you try to move out of a member of a mutably borrowed struct, in which case `mem::replace` can help. Mentioning that here hopefully saves future users a trip to Google.
update tests emitter.rs
There is no `Drop` implemented for `Child`, so if it goes out of scope in Rust-land and gets deallocated, the child process will continue to exist and execute. If users want a guarantee that the process has finished running and exited they must manually use `kill`, `wait`, or `wait_with_output`. Fixes rust-lang#31289.
Spelling mistake - `familliar` > `familiar`
This matches the usage in the standard library's documentation.
Some other shufflings as well: * Three powerpc triples for Linux have been added recently * An armv7 linux triple was added recently * The 64-bit Solaris triple is now mentioned in tier 3 We are currently now also building nightlies for iOS, powerpc triples, and armv7, but there hasn't been much vetting of the triples themselves so I've left them in tier 3 for now.
Updated documentation to clarify the difference between `and_then` and `map`. This also explains why we need `and_then` in addition to `map`. Please look at the diff for more information. r? @alexcrichton
Fixes rust-lang#30459 Fun fact: i wanted to write "Arabic" and "Hebrew" in Arabic and Hebrew, but vim kept doing the copy/paste in the wrong direction.
E0507 can occur when you try to move out of a member of a mutably borrowed struct, in which case `mem::replace` can help. Mentioning that here hopefully saves future users a trip to Google.
…, r=alexcrichton `Drop` is not implemented for `Child`, so if it goes out of scope in Rust-land and gets deallocated the child process will continue to exist and execute. If users want a guarantee that the process has finished running and exited they must manually use `kill`, `wait`, or `wait_with_output`. Fixes rust-lang#31289. r? @steveklabnik
👀 Test was successful, but fast-forwarding failed: 500 Server Error |
👀 Test was successful, but fast-forwarding failed: 500 Server Error |
👀 Test was successful, but fast-forwarding failed: 500 Server Error |
5 similar comments
👀 Test was successful, but fast-forwarding failed: 503 Repository offline |
👀 Test was successful, but fast-forwarding failed: 503 Repository offline |
👀 Test was successful, but fast-forwarding failed: 503 Repository offline |
map
andand_then
with an example. #30971, Document LTR vs RTL wrt trim_* #31202, doc: bindings not needed for this example #31247, Improve message for rustc --explain E0507 #31270, fix overflow due to multiline error span #31281, Safety docs about process::Child going out of scope #31327, Update TESTNAME instructions in CONTRIBUTING.md #31339, Fix typo in doc/book/getting-started.md #31340, Comment fix #31342, make this example more obvious #31344, book: Change "Failures" to "Errors" in doc special sections chapter #31345, Fix a documentation typo #31346, doc: Move 32-bit MSVC to a tier 1 platform #31348