Skip to content

Rollup of 5 pull requests - #102726

Merged
bors merged 13 commits into
rust-lang:masterfrom
matthiaskrgr:rollup-2ghn38b
Oct 6, 2022
Merged

Rollup of 5 pull requests#102726
bors merged 13 commits into
rust-lang:masterfrom
matthiaskrgr:rollup-2ghn38b

Conversation

@matthiaskrgr

Copy link
Copy Markdown
Member

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

BlackHoleFoxand others added 13 commits October 5, 2022 00:48
Co-authored-by: nils <48135649+Nilstrieb@users.noreply.github.com>
…changes, r=thomcc
Revert "Use getentropy when possible on all Apple platforms"
Per rust-lang#102643, This reverts commit 3fc35b5 to avoid breaking any Rust on iOS users.
Closesrust-lang#102643
…vidtwco
Suggest calling method if fn does not exist
I tried to split this up into two commits, the first where we stash the resolution error until typeck (which causes a bunch of diagnostics changes because the ordering of error messages change), then the second commit is the actual logic that actually implements the suggestion.
I am not in love with the presentation of the suggestion, so I could use some advice for how to format the actual messaging.
r? diagnostics
Fixesrust-lang#102518
…=estebank
Suggest `==` to wrong assign expr
Given the following code:
```rust
fn main() {
let x = 3;
let y = 3;
if x == x && y = y {
println!("{}", x);
}
}
```
Current output is:
```
error[E0308]: mismatched types
--> src/main.rs:4:18
|
4 | if x == x && y = y {
| ^ expected `bool`, found integer
error[E0308]: mismatched types
--> src/main.rs:4:8
|
4 | if x == x && y = y {
| ^^^^^^^^^^^^^^^ expected `bool`, found `()`
```
This adds a suggestion:
```diff
error[E0308]: mismatched types
--> src/main.rs:6:18
|
6 | if x == x && y = y {
| ^ expected `bool`, found integer
error[E0308]: mismatched types
--> src/main.rs:6:8
|
6 | if x == x && y = y {
| ^^^^^^^^^^^^^^^ expected `bool`, found `()`
|
+ help: you might have meant to compare for equality
+ |
+ 6 | if x == x && y == y {
+ | +
```
And this fixes a part of rust-lang#97469
…, r=estebank
Add test for issue 82633
Fixesrust-lang#82633
r? `@estebank`
The current stderr looks slightly different from [source](https://github.com/rust-lang/rust/pull/83915/files#diff-8c64c576ccaceb816e71d2279a6ee4bf79211bc06f55c46dda3f98a18748ad7a), so I used the latest one from nightly. Do let me know if anything is wrong.
@rustbotrustbot added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Oct 6, 2022
@matthiaskrgr

Copy link
Copy Markdown
MemberAuthor

@bors r+ rollup=never p=5

@bors

bors commented Oct 6, 2022

Copy link
Copy Markdown
Collaborator

📌 Commit b7642fb has been approved by matthiaskrgr

It is now in the queue for this repository.

@borsbors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Oct 6, 2022
@bors

bors commented Oct 6, 2022

Copy link
Copy Markdown
Collaborator

⌛ Testing commit b7642fb with merge 4bd3078...

@bors

bors commented Oct 6, 2022

Copy link
Copy Markdown
Collaborator

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 4bd3078 to master...

@borsbors added the merged-by-bors This PR was explicitly merged by bors. label Oct 6, 2022
@bors
bors merged commit 4bd3078 into rust-lang:masterOct 6, 2022
@rustbotrustbot added this to the 1.66.0 milestone Oct 6, 2022
@rust-timer

Copy link
Copy Markdown
Collaborator

📌 Perf builds for each rolled up PR:

PR#Perf Build Sha
#102710eab985bc2a82f434746bd9d20c8ffe32bcf388ae
#102708ab3e436e1ce08e725bfa1fa7948227d3b0a82857
#102694852ff0e26ec23f5a4bd22d343a1d3d9ee89160eb
#102693417e67285053844806a77c4cf1e3fd58c760501d
#10267226dd9a8f5c5eff721530528a999c741b5a9871dc

previous master: 0152393048

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (4bd3078): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

mean1rangecount2
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
--0
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
-1.1%[-1.1%, -1.1%]1
All ❌✅ (primary)--0

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean1rangecount2
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
2.2%[2.2%, 2.3%]2
Improvements ✅
(primary)
-3.0%[-3.0%, -3.0%]1
Improvements ✅
(secondary)
-3.0%[-3.0%, -3.0%]1
All ❌✅ (primary)-3.0%[-3.0%, -3.0%]1

Cycles

This benchmark run did not return any relevant results for this metric.

Footnotes

  1. the arithmetic mean of the percent change2

  2. number of relevant changes2

@matthiaskrgr
matthiaskrgr deleted the rollup-2ghn38b branch October 9, 2022 00:31
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-borsThis PR was explicitly merged by bors.rollupA PR which is a rollupS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants

@matthiaskrgr@bors@rust-timer@rustbot@BlackHoleFox@compiler-errors@TaKO8Ki@Rageking8@notriddle