-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Change xfail
directives in compiletests to ignore
#11363
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Comments
Are you referring to Markdown file |
bors
added a commit
that referenced
this issue
Feb 12, 2014
While working on #11363 I stumbled over a couple of ignored tests, that seem to be fixed or invalid. * src/test/run-pass/issue-3559.rs was fixed in #4726 * src/test/compile-fail/borrowck-call-sendfn.rs was fixed in #2978 * update src/test/compile-fail/issue-5500-1.rs to work with current Rust (I'm not 100% sure if the original condition is tested as mentioned in #5500, but I think so) * removed src/test/compile-fail/issue-5500.rs because it is tested in src/test/run-fail/issue-5500.rs (they are the same test cases, I just renamed src/test/run-fail/addr-of-bot.rs to be consistent with the other issue name
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Dec 1, 2023
…re_call_on_closure_returns_async_block, r=llogiq [`redundant_closure_call`]: avoid duplicated `async` keyword when triggering on closure that returns `async` block close rust-lang#11357 ---- *Please write a short comment explaining your change (or "none" for internal only changes)* changelog: [`redundant_closure_call`]: avoid duplicated `async` keyword when triggering on closure that returns `async` block
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Similar to #11362. It's long bugged me that we use two different terms for this.
The text was updated successfully, but these errors were encountered: