Skip to content

Conversation

smoelius
Copy link
Contributor

@smoelius smoelius commented Oct 10, 2025

Resolves #15780.

I didn't get any feedback on that issue. So I hope it is okay that I charged ahead and addressed it.

changelog: Allow explicit_write in tests

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties label Oct 10, 2025
@rustbot
Copy link
Collaborator

rustbot commented Oct 10, 2025

r? @Jarcho

rustbot has assigned @Jarcho.
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

@rustbot

This comment has been minimized.

Comment on lines +55 to +58
if is_in_test(cx.tcx, expr.hir_id) {
return;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could pull this into the let-chain

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was afraid that would confuse the logic. If it's okay, I'd like to wait and see what @Jarcho says.

@smoelius smoelius force-pushed the allow-explicit-write-in-tests branch from 720f1f5 to 1eb9a09 Compare October 11, 2025 10:29
@rustbot
Copy link
Collaborator

rustbot commented Oct 11, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Disable explicit_write in test code?

4 participants