Add better error message for partial move

[clintfred]

closes#56657

r? @davidtwco

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @davidtwco (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[clintfred]

I have several tests failing on my branch, but am hoping this PR will allow others to help me move forward.

[davidtwco]

@clintfred Excited to see this PR! Could you update those test outputs and add them to the PR so that we can see what outputs you are getting and add review comments with steps to take?

[clintfred]

@clintfred Excited to see this PR! Could you update those test outputs and add them to the PR so that we can see what outputs you are getting and add review comments with steps to take?

@davidtwco I'm not sure I understand your request. Won't we see the failing tests when CI runs? Or does it run only some intelligent subset of the tests based on what's changed?

[davidtwco]

@clintfred We will, but it's easier to put review comments and have discussions on your changes than the test results.

[estebank]

@clintfred you can run ./x.py test src/test/ui --stage 1 --bless, which will update the .stderr files. After doing that I think the PR can be approved. You can see the current test errors in Travis (they all seem to be stderr output mismatch and nothing else).

[clintfred]

@estebank I think that's the same set of failures I was seeing on my machine, so that's a good sign. When reviewing them on my own, it wasn't clear to me that all of those error messages were correct after my change. I will look again, but I would appreciate confirmation from others that they look correct as well.

I will run with --bless so we can get all the files into this PR regardless per @davidtwco's instructions.

[davidtwco]

Looking great. Here are some small changes.

[clintfred]

I have implemented the suggested changes. Some tests will start failing again and hopefully they will be all the tests that were previously erroneously marked as partial moves... If so, I can rerun the --bless

[estebank]

https://travis-ci.com/rust-lang/rust/jobs/177505407#L2819

[davidtwco]

travis-ci.com/rust-lang/rust/jobs/177505407#L2819

A quick glance makes me think that these are all correct. Feel free to bless and push @clintfred.

[estebank]

@bors r+

[bors]

📌 Commit de05548 has been approved by estebank

[bors]

🌲 The tree is currently closed for pull requests below priority 160, this pull request will be tested once the tree is reopened

[estebank]

Oh, sorry, didn't realize that you were the reviewer, @davidtwco. Feel free to r- if you disagree.

[davidtwco]

Oh, sorry, didn't realize that you were the reviewer, @davidtwco. Feel free to r- if you disagree.

No worries, this looks great! Thanks @clintfred!

[kennytm]

@bors r- rollup-

Failed in NLL mode in #58566 (comment). Needs to update the text (bless) these 6 test cases:

[01:30:22] failures:
[01:30:22] [ui (nll)] ui/borrowck/borrowck-uninit-field-access.rs#ast
[01:30:22] [ui (nll)] ui/moves/moves-based-on-type-cyclic-types-issue-4821.rs
[01:30:22] [ui (nll)] ui/moves/moves-based-on-type-match-bindings.rs
[01:30:22] [ui (nll)] ui/ref-suggestion.rs
[01:30:22] [ui (nll)] ui/unsized-locals/borrow-after-move.rs
[01:30:22] [ui (nll)] ui/unsized-locals/double-move.rs

[clintfred]

@kennytm I'll take a look.

[estebank]

I think all you have to do is run the same ./x.py ... --bless command with --compare-mode=nll to update these files.

[estebank]

@bors r+ rollup

[bors]

📌 Commit 02fe6a7 has been approved by estebank

[estebank]

@bors rollup-

[clintfred]

@estebank I'm not sure of the status here. Do I need to do anything?

[estebank]

@clintfred not for the moment, I removed the rollup because this has the potential to clash with other PRs that incorporate partial move errors. Because the stderr files would be new, and generated from a parent commit that didn't have your changes there would be no merge conflict, but the tests would fail because of the discrepancy between both changes. This PR is still approved and will be merged on its own. There's the potential of a different PR being merged in the meantime that will necessitate you to rebase and re-bless, but no other action will be required of you.

Thank you for all the effort you've put into this! These small incremental improvements add up and are critical to maintaining the quality we want to see in rustc.