summaryrefslogtreecommitdiffstats
path: root/tests/ui/async-await/task-context-arg.rs
diff options
context:
space:
mode:
Diffstat (limited to 'tests/ui/async-await/task-context-arg.rs')
-rw-r--r--tests/ui/async-await/task-context-arg.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/ui/async-await/task-context-arg.rs b/tests/ui/async-await/task-context-arg.rs
index 937723ca7..45b18d56b 100644
--- a/tests/ui/async-await/task-context-arg.rs
+++ b/tests/ui/async-await/task-context-arg.rs
@@ -10,7 +10,7 @@
use std::future::Future;
// The compiler produces a closure as part of this function. That closure initially takes an
-// argument _task_context. Later, when the MIR for that closure is transformed into a generator
+// argument _task_context. Later, when the MIR for that closure is transformed into a coroutine
// state machine, _task_context is demoted to not be an argument, but just part of an unnamed
// argument. If we emit debug info saying that both _task_context and the unnamed argument are both
// argument number 2, then LLVM will fail with "conflicting debug info for argument". See