moves from unsafe ptrs / initializers

[nikomatsakis]

Today we accept this:

let i <- *p

where p is an unsafe ptr. This is ok. However, I think we accept it because we are not properly checking for moves in initializers and not for any good reason. We should probably accept moves out of unsafe ptrs (it's useful) but also check initializers properly. I'm not sure whether this is a borrowck or liveness bug but I think borrowck.

[catamorphism]

Obsolete since we don't have <- anymore.

[rust-log-analyzer]

The job x86_64-gnu-llvm-13 failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

    Finished dev [unoptimized] target(s) in 0.06s
Skipping Set({test::src/tools/tidy}) because it is excluded
Skipping Set({test::src/tools/tidy}) because it is excluded
Building stage0 std artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
error: the lock file /checkout/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.