Skip to content
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 14 pull requests #88527

Merged
merged 38 commits into from
Aug 31, 2021
Merged

Rollup of 14 pull requests #88527

merged 38 commits into from
Aug 31, 2021

Conversation

m-ou-se
Copy link
Member

@m-ou-se m-ou-se commented Aug 31, 2021

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

ChrisDenton and others added 30 commits August 27, 2021 14:25
It might not be obvious that the "path of the current running executable" may (or may not) mean "at the time it was loaded".
Old error output:

   = note: this warning originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info)
help: wrap this expression in parentheses
   |
4  |             break '_l $f(;)
   |                         ^ ^

New error output:

   = note: this warning originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info)
help: wrap this expression in parentheses
   |
4  |             break '_l ($f);
   |                       ^  ^
Old error output:

    3  |         let _: usize = $f;
       |                -----     ^ expected `usize`, found struct `Baz`
       |                |
       |                expected due to this

New error output:

    3  |         let _: usize = $f;
       |                -----   ^^ expected `usize`, found struct `Baz`
       |                |
       |                expected due to this
And adding missing link to Duration from Instant
MaybeUninit::write is stable as of 1.55.0.
Document `std::env::current_exe` possible rename behaviour

It might not be obvious that the "path of the current running executable" may (or may not) imply "at the time it was loaded".

This came up recently in chat so I thought it might be worth documenting.
…oli-obk

Tait nest infer test

r? `@oli-obk`

Related to rust-lang#86727
…t, r=oli-obk

Add inference cycle TAIT test

r? `@oli-obk`

Related to rust-lang#86727
…=oli-obk

Add auto trait leakage TAIT test

r? `@oli-obk`

Related to rust-lang#86727
…test, r=oli-obk

Add weird return types TAIT test

r? `@oli-obk`

Related to rust-lang#86727
…r, r=cjgillot

fix(rustc_parse): correct span in `maybe_whole_expr!`

Fixes rust-lang#87812
rustdoc: Stop using resolver for macro loading

r? `@jyn514`
Adding examples to docs of `std::time` module

And adding missing link to `Duration` from `Instant`.
…iser

Use MaybeUninit::write in functor.rs

MaybeUninit::write is stable as of 1.55.0.
…generics, r=petrochenkov

Fix prelude collision lint suggestion for generics with lifetimes

Fixes rust-lang#88470

cc `@nikomatsakis`
…ikomatsakis

Fix prelude collision suggestions for glob imported traits.

Fixes rust-lang#88471

cc `@nikomatsakis`
… r=cjgillot

Warn when [T; N].into_iter() is ambiguous in the new edition.

Fixes rust-lang#88475

In rust-lang#88475, a situation was found where `[T; N].into_iter()` becomes *ambiguous* in the new edition. This is different than the case where `(&[T; N]).into_iter()` resolves differently, which was the only case handled by the `array_into_iter` lint. This is almost identical to the new-traits-in-the-prelude problem. Effectively, due to the array-into-iter hack disappearing in Rust 2021, we effectively added `IntoIterator` to the 'prelude' in Rust 2021 specifically for arrays.

This modifies the prelude collisions lint to detect that case and emit a `array_into_iter` lint in that case.
…ft-just-single-angle-brackets-please-thanks, r=petrochenkov

Don't suggest extra <> in dyn suggestion.

Fixes rust-lang#88508
@rustbot rustbot added the rollup A PR which is a rollup label Aug 31, 2021
@m-ou-se
Copy link
Member Author

m-ou-se commented Aug 31, 2021

@bors r+ p=5 rollup=never

@bors
Copy link
Contributor

bors commented Aug 31, 2021

📌 Commit feafda8 has been approved by m-ou-se

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Aug 31, 2021
@bors
Copy link
Contributor

bors commented Aug 31, 2021

⌛ Testing commit feafda8 with merge 76d18cf...

@bors
Copy link
Contributor

bors commented Aug 31, 2021

☀️ Test successful - checks-actions
Approved by: m-ou-se
Pushing 76d18cf to master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants