-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Backport: Switch #[track_caller]
back to a no-op unless feature gate is enabled
#106188
Backport: Switch #[track_caller]
back to a no-op unless feature gate is enabled
#106188
Conversation
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
|
cc @davidtwco, @compiler-errors, @JohnTitor, @estebank, @TaKO8Ki |
backport looks totally as expected -- r=me, idk if it needs an approval from the release team or something since it's beta |
@bors r=compiler-errors rollup=never No, so long as beta backport is approved this is enough. |
☀️ Test successful - checks-actions |
Backport of #104741
r? @compiler-errors since you reviewed the original PR
requested by @Mark-Simulacrum #104741 (comment)