-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Create separate feature gate for #[track_caller]
on async fn
#110009
Labels
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
Comments
bryangarza
changed the title
Create separate feature flag for
Create separate feature gate for Apr 6, 2023
#[track_caller]
on async fn#[track_caller]
on async fn
4 tasks
@rustbot claim |
@rustbot label +T-lang |
rustbot
added
the
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
label
Apr 6, 2023
Friendly ping @bryangarza, are you still working on / planning to work on this? |
@tmandry I can work on it next week! Haven’t started yet. |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Aug 4, 2023
…, r=compiler-errors Add separate feature gate for async fn track caller This patch adds a feature gate `async_fn_track_caller` that is separate from `closure_track_caller`. This is to allow enabling `async_fn_track_caller` separately. Fixes rust-lang#110009
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
#[track_caller]
on async fn depends on#![feature(closure_track_caller)]
.We want to make this a separate feature gate now, so that
#[track_caller]
on async fn can be independently toggled on.feature gate name:
async_fn_track_caller
See comment at: #87417 (comment)
The text was updated successfully, but these errors were encountered: