Fixes rust-lang#52524.

Fixes the clippy "single_char_pattern" lint, and (marginally) improves
performance.

Fixes a clippy warning, and improves readability.

Use `.nth(n)` rather than `.skip(n).next()` (also fixes a clippy
warning), and use `.into()` and a type signature rather than
`PathBuf::from`.

Eliminates a clippy warning.

Also drop the unnecessary `.peekable()`.

Also eliminates a clippy lint.

…fetimes

Dropping the redundant lifetimes also eliminates a clippy warning.

This also eliminates a clippy warning.

Drop unnecessary .into_iter() (also fixing a clippy warning), and use
path functions to handle file extensions.

This makes the code more readable, and eliminates a clippy warning.

This improves readability and eliminates a clippy warning.

Use `if let` to simplify a match, and use `contains_key` instead of
`get`.

The match expression immediately below it checks the same condition.

Mention that you can use `into_inner` to drop the contained value.

…-lang#52934.

Fixes a problem where submodules could not be cloned under some git
configurations. Specifically, when url.git@github.com:.insteadOf =
https://github.com/ is set.

If a suitable value of Python is not on PATH, one can still invoke x.py
manually, which propagates BOOTSTRAP_PYTHON into the bootstrap
environment.  But building LLVM will abort with error messages about not
being able to find Python, and instructions to set PYTHON_EXECUTABLE,
because nothing is done with BOOTSTRAP_PYTHON when invoking cmake.
Setting build.python in config.toml had no effect in this scenario,
either

To fix this, let's provide PYTHON_EXECUTABLE when invoking cmake; for
the "normal" case of Python in PATH, this doesn't alter any behavior.
For more unusual cases, however, this ensures cmake finds Python
properly.  (This change also ensures there are no differences between
what bootstrap is using, and what cmake uses, which may be useful for
consistency's sake.)

Added in rust-lang#52149 the discussion in rust-lang#53514 is showing how we may not want to
actually add this attribute to the atomic types. While we continue to
debate rust-lang#53514 this commit reverts the addition of the `transparent` attribute.
This should be a more conservative route which leaves us the ability to tweak
this in the future but in the meantime allows us to continue discussion as well.

…pass/`.

(I may have accidentally added it to some auxilliary crates as well;
my emacs-macro-based methodology was pretty crude.)

…o silence stderr output.

…(C)`.

See also rust-lang#53858.

…est seems bogus.

that is, I suspect it should be retired because it is testing behavior
(namely a `#[repr(C)] struct Empty;`) that, if I understand correctly,
is undefined.

See also rust-lang#53859.

See rust-lang#53857.

…ced).

…s to test such cases.

…pdated at some point.

Discussion can be found on rust-lang#41620.

…d to `#[may_dangle]`.

See rust-lang#34761.

…t be silenced.

That is, opting to ignore stable `#![feature(..)]`, under my theory
that a reviewer would prefer as much stuff to be bucketed under "ah
another `#![allow(..)]` here." as possible.

…se on 32-bit.

Just shuffling files here; the needed updates to content come later.

…i/run-pass/`.

(or generics that *might* have dtors)

…pdated at some point.

Discussion can be found on rust-lang#41620.

updates to cafef7b

…veklabnik

Updated core/macros.rs to note it works in a no_std environment.

Fixes rust-lang#45797
This PR updates the documentation of `write!` to note it works in a `no_std` environment, and adds an
example to showcase this. In a `no_std` environment, the author of the code is responsible for the
implementation of the `Write` trait. This example will work out of the box with `no_std`, but the
implementation of `Write` is expected to be provided by the user.

r? @steveklabnik

…Gomez

Cross reference io::copy and fs::copy in docs.

Fixes rust-lang#52524.

…steveklabnik

Individual docs for {from,to}_*_bytes

librustc_lint: In recursion warning, change 'recurring' to 'recursing'

The existing wording seems incorrect.

Aside: This warning, 'function cannot return without recursing' is not perfectly clear - it implies that the function _can_ return, it's just got to recurse. But really the fn cannot return period. Clearer wording: 'function recurses infinitely; it cannot return'; or 'function is infinitely self-recursive; it cannot return, and this is probably an error'. I like that.

…ss-to-ui, r=nikomatsakis

Migrate (some) of run-pass/ to ui

This is a step towards addressing rust-lang#53764. Much still remains.

I went through a large portion of the `*.rs` files that were directly stored into `src/test/run-pass/` and moved them into various subdirectories of a newly created `src/test/ui/run-pass/`.

(yes, it would have perhaps been nice to meld it more directly with directories already in `src/test/ui/`; but the sad truth is that opens up the reality of filename collisions, and one of my short term goals for resolving rust-lang#53764 is to keep the *filenames* invariant, even as their parents directories and contents are mildly revised...)

Implement Unpin for Box, Rc, and Arc

Per the discussion in rust-lang#49150, these should implement `Unpin` even if what they point to does not.

tidy: Cleanups and clippy warning fixes

This eliminates various clippy warnings in the tidy tool, as well as
making some related cleanups. These changes should not introduce any
functional differences.

Clarify `ManuallyDrop` docs

Mention that you can use `into_inner` to drop the contained value.

…y-test, r=wesleywiser

Minimized clippy test from when NLL disabled two-phase borrows

(Of course anyone even skimming the test will realize that this is an *expansion* of a previously posted [minimization](rust-lang#52934 (comment)).)

Fix rust-lang#52934.

Add .git extension to submodule paths missing it

Fixes a problem where submodules could not be cloned under some git
configurations. Specifically, when url.git@github.com:.insteadOf =
https://github.com/ is set.

…ebank

A few cleanups and minor improvements to mir/dataflow

- simplify `dot::GraphWalk::edges` and optimize its vector's allocation
- turn a `kill` loop into `kill_all`
- remove the `prepost` parameter from `dataflow_path` (it doesn't seem to do anything)
- a couple of other minor improvements

…alexcrichton

propagate build.python into cmake

If a suitable value of Python is not on `PATH`, one can still invoke x.py
manually, which propagates `BOOTSTRAP_PYTHON` into the bootstrap
environment.  But building LLVM will abort with error messages about not
being able to find Python, and instructions to set `PYTHON_EXECUTABLE`,
because nothing is done with `BOOTSTRAP_PYTHON` when invoking cmake.
Setting `build.python` in config.toml had no effect in this scenario,
either

To fix this, let's provide `PYTHON_EXECUTABLE` when invoking cmake; for
the "normal" case of Python in `PATH`, this doesn't alter any behavior.
For more unusual cases, however, this ensures cmake finds Python
properly.  (This change also ensures there are no differences between
what bootstrap is using, and what cmake uses, which may be useful for
consistency's sake.)

…t-atomics-master, r=sfackler

Remove `#[repr(transparent)]` from atomics

Added in rust-lang#52149 the discussion in rust-lang#53514 is showing how we may not want to
actually add this attribute to the atomic types. While we continue to
debate rust-lang#53514 this commit reverts the addition of the `transparent` attribute.
This should be a more conservative route which leaves us the ability to tweak
this in the future but in the meantime allows us to continue discussion as well.

…s, r=oli-obk

Add unchecked_shl/shr check for intrinsics to fix miri's test suit

r? @RalfJung

cc @oli-obk

rust-lang#53697 broke miri's test suite as described in [this comment](rust-lang#53697 (comment)). This PR adds test for the `unchecked_shr/shl` for the intrinsics.

…ss-borrowck-to-ui, r=nikomatsakis

migrate run-pass/borrowck to ui/run-pass

Part of rust-lang#53764

…ss-dirs-to-ui, r=alexcrichton

migrate run-pass/*/ to ui/run-pass

I think this is all that remains of rust-lang#53764

update clippy submodule

updates to cafef7b