Skip to content

Conversation

jdonszelmann
Copy link
Contributor

In this PR I noticed that we don't sort attribute targets, so a rather trivial change to the source changed the ordering in an error message even though its meaning stayed the same.

See: #147418 (comment)

I think sorting might be a good thing to do in general. I also prefer it when reading error messages. Quite a few tests changed, but not in meaning, only sorting order obviously.

r? @jieyouxu

@rustbot
Copy link
Collaborator

rustbot commented Oct 7, 2025

This PR modifies tests/ui/issues/. If this PR is adding new tests to tests/ui/issues/,
please refrain from doing so, and instead add it to more descriptive subdirectories.

@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Oct 7, 2025
@rustbot
Copy link
Collaborator

rustbot commented Oct 7, 2025

jieyouxu is not on the review rotation at the moment.
They may take a while to respond.

@rustbot

This comment has been minimized.

@jdonszelmann
Copy link
Contributor Author

(range diff is very useful here, neat)

@bors
Copy link
Collaborator

bors commented Oct 7, 2025

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

@rustbot
Copy link
Collaborator

rustbot commented Oct 8, 2025

This PR was rebased onto a different master 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.

@WaffleLapkin
Copy link
Member

@bors delegate=@JonathanBrouwer

@bors
Copy link
Collaborator

bors commented Oct 8, 2025

✌️ @JonathanBrouwer, you can now approve this pull request!

If @WaffleLapkin told you to "r=me" after making some further change, please make that change, then do @bors r=@WaffleLapkin

@JonathanBrouwer
Copy link
Contributor

@bors r+

@bors
Copy link
Collaborator

bors commented Oct 8, 2025

📌 Commit 1dbe831 has been approved by JonathanBrouwer

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 8, 2025
@JonathanBrouwer
Copy link
Contributor

@bors rollup

bors added a commit that referenced this pull request Oct 8, 2025
Rollup of 5 pull requests

Successful merges:

 - #146385 (rustdoc-search: redesign throbber to be less distracting)
 - #147390 (Use globals instead of metadata for std::autodiff)
 - #147445 (sort attribute targets for more consistent error messages)
 - #147448 (collect-license-metadata: update submodules before running)
 - #147451 (fix panic with extra-const-ub-checks)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 4f24b61 into rust-lang:master Oct 8, 2025
10 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Oct 8, 2025
rust-timer added a commit that referenced this pull request Oct 8, 2025
Rollup merge of #147445 - jdonszelmann:sort-targets, r=JonathanBrouwer

sort attribute targets for more consistent error messages

In this PR I noticed that we don't sort attribute targets, so a rather trivial change to the source changed the ordering in an error message even though its meaning stayed the same.

See: #147418 (comment)

I think sorting might be a good thing to do in general. I also prefer it when reading error messages. Quite a few tests changed, but not in meaning, only sorting order obviously.

r? `@jieyouxu`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-attributes Area: Attributes (`#[…]`, `#![…]`) S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants