Skip to content

actually make the is-fn test test what it says it tests #153762

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.

Sign up for GitHub

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

Merged
rust-bors merged 1 commit into from
Mar 12, 2026
Merged

actually make the is-fn test test what it says it tests #153762

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tests/ui/async-await/async-closures/is-fn.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,11 @@ use std::future::Future;

extern crate block_on;

// Check that closures that don't capture any state may implement `Fn`.
// Check that async closures that don't capture any state may implement `Fn`.

fn main() {
block_on::block_on(async {
async fn call_once<F: Future>(x: impl FnOnce(&'static str) -> F) -> F::Output {
async fn call_once<F: Future>(x: impl Fn(&'static str) -> F) -> F::Output {
x("hello, world").await
}
call_once(async |x: &'static str| {
Expand Down
Loading