summaryrefslogtreecommitdiffstats
path: root/src/test/ui/async-await/issues/issue-64391-2.rs
diff options
context:
space:
mode:
Diffstat (limited to 'src/test/ui/async-await/issues/issue-64391-2.rs')
-rw-r--r--src/test/ui/async-await/issues/issue-64391-2.rs20
1 files changed, 0 insertions, 20 deletions
diff --git a/src/test/ui/async-await/issues/issue-64391-2.rs b/src/test/ui/async-await/issues/issue-64391-2.rs
deleted file mode 100644
index eef2c1fb2..000000000
--- a/src/test/ui/async-await/issues/issue-64391-2.rs
+++ /dev/null
@@ -1,20 +0,0 @@
-// Regression test for #64391
-//
-// As described on the issue, the (spurious) `DROP` inserted for the
-// `"".to_string()` value was causing a (spurious) unwind path that
-// led us to believe that the future might be dropped after `config`
-// had been dropped. This cannot, in fact, happen.
-//
-// check-pass
-// edition:2018
-
-async fn connect() {
- let config = 666;
- connect2(&config, "".to_string()).await
-}
-
-async fn connect2(_config: &u32, _tls: String) {
- unimplemented!()
-}
-
-fn main() { }