summaryrefslogtreecommitdiffstats
path: root/tests/ui/impl-trait/lifetime-ambiguity-regression.rs
diff options
context:
space:
mode:
Diffstat (limited to 'tests/ui/impl-trait/lifetime-ambiguity-regression.rs')
-rw-r--r--tests/ui/impl-trait/lifetime-ambiguity-regression.rs13
1 files changed, 13 insertions, 0 deletions
diff --git a/tests/ui/impl-trait/lifetime-ambiguity-regression.rs b/tests/ui/impl-trait/lifetime-ambiguity-regression.rs
new file mode 100644
index 000000000..ce6ae3786
--- /dev/null
+++ b/tests/ui/impl-trait/lifetime-ambiguity-regression.rs
@@ -0,0 +1,13 @@
+//! This test shows a situation where through subtle compiler changes we can
+//! suddenly infer a different lifetime in the hidden type, and thus not meet
+//! the opaque type bounds anymore. In this case `'a` and `'b` are equal, so
+//! picking either is fine, but then we'll fail an identity check of the hidden
+//! type and the expected hidden type.
+
+// check-pass
+
+fn test<'a: 'b, 'b: 'a>() -> impl IntoIterator<Item = (&'a u8, impl Into<(&'b u8, &'a u8)>)> {
+ None::<(_, (_, _))>
+}
+
+fn main() {}