Added file check to mir-opt/return_an_array.rs

[milosilo-dev]

I have added file checks to this file after reading #116971, I have only done one file because i want some feedback on weather I am doing it correctly or weather I am confused.

Any feedback would be greatly appreciated!

[rustbot]

r? @jieyouxu

rustbot has assigned @jieyouxu.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Fallback group: @Mark-Simulacrum, @jieyouxu
• @Mark-Simulacrum, @jieyouxu expanded to Mark-Simulacrum, jieyouxu
• Random selection from Mark-Simulacrum, jieyouxu

[jieyouxu]

r? mir-opt

[cjgillot]

This looks like an ancient test to mark destination propagation as a desired feature. We have a dedicated mir-opt test suite for this.

Do you mind?

• moving this test in test/mir-opt/dest-prop directory,
• add the following comment at the top of the file

//@ test-mir-pass: DestinationPropagation

View changes since this review

[cjgillot]

This is clearer than the current toplevel comment. Do you mind making this the toplevel doc-comment?

[cjgillot]

I usually prefer having the checks start with a // CHECK-LABEL: fn foo( and to appear inside the corresponding function.

[milosilo-dev]

This has been added to the PR

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[rustbot]

⚠️ Warning ⚠️

• The following commits have merge commits (commits with multiple parents) in your changes. We have a no merge policy so these commits will need to be removed for this pull request to be merged.

  • ed25c44

  You can start a rebase with the following commands:

  $ # rebase
  $ git pull --rebase https://github.com/rust-lang/rust.git main
  $ git push --force-with-lease
  

[rust-bors]

☔ The latest upstream changes (presumably #155674) made this pull request unmergeable. Please resolve the merge conflicts.