-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch #[track_caller]
back to a no-op unless feature gate is enabled
#104741
Switch #[track_caller]
back to a no-op unless feature gate is enabled
#104741
Conversation
r? @jackh726 (rustbot has picked a reviewer for you, use r? to override) |
cc @davidtwco, @compiler-errors, @JohnTitor, @estebank, @TaKO8Ki |
7d748cd
to
e589c06
Compare
src/test/ui/async-await/track-caller/issue-104588-no-op-track-caller.stderr
Outdated
Show resolved
Hide resolved
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. I had some questions, though I may be missing some context, so feel free to correct me if I assumed something incorrectly.
src/test/ui/async-await/track-caller/issue-104588-no-op-panic-track-caller.rs
Outdated
Show resolved
Hide resolved
I addressed most of the comments and resolved their threads, but there's a couple more I have to follow up with in another commit :) |
|
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #104863) made this pull request unmergeable. Please resolve the merge conflicts. |
My latest commit is near-identical to #105180 so I think I will need to just remove that one and rebase (there might be a couple lines to keep from the commit, but not related to the hirId) |
882873a
to
38f8561
Compare
@rustbot ready |
Thanks for the comments! I’ll update this PR soon |
☔ The latest upstream changes (presumably #105667) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r+ rollup |
Beta nominating this because this fixes a regression that's currently stable-to-beta (introduced in #104219) where |
…caller, r=compiler-errors Switch `#[track_caller]` back to a no-op unless feature gate is enabled This patch fixes a regression, in which `#[track_caller]`, which was previously a no-op, was changed to actually turn on the behavior. This should instead only happen behind the `closure_track_caller` feature gate. Also, add a warning for the user to understand how their code will compile depending on the feature gate being turned on or not. Fixes rust-lang#104588
…iaskrgr Rollup of 8 pull requests Successful merges: - rust-lang#104741 (Switch `#[track_caller]` back to a no-op unless feature gate is enabled) - rust-lang#105769 (add function to tell the identical errors for ambiguity_errors) - rust-lang#105843 (Suggest associated const on possible capitalization mistake) - rust-lang#105966 (Re-enable `Fn` trait call notation error for non-tuple argument) - rust-lang#106002 (codegen tests: adapt patterns to also work with v0 symbol mangling) - rust-lang#106010 (Give opaque types a better coherence error) - rust-lang#106016 (rustdoc: simplify link anchor to section expand JS) - rust-lang#106024 (Fix ICE due to `todo!()` in `rustdoc` for `Term`s) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
This PR does not backport cleanly -- @bryangarza would you be able to prepare a PR targeting the beta branch? |
Sounds good, I'll create the backport PR |
…ller_beta-backport, r=compiler-errors Backport: Switch `#[track_caller]` back to a no-op unless feature gate is enabled Backport of rust-lang#104741 r? `@compiler-errors` since you reviewed the original PR requested by `@Mark-Simulacrum` rust-lang#104741 (comment)
This patch fixes a regression, in which
#[track_caller]
, which was previously a no-op, was changed to actually turn on the behavior. This should instead only happen behind theclosure_track_caller
feature gate.Also, add a warning for the user to understand how their code will compile depending on the feature gate being turned on or not.
Fixes #104588