summaryrefslogtreecommitdiffstats
path: root/src/test/ui/mir/mir-typeck-normalize-fn-sig.rs
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-17 12:19:03 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-17 12:19:03 +0000
commit64d98f8ee037282c35007b64c2649055c56af1db (patch)
tree5492bcf97fce41ee1c0b1cc2add283f3e66cdab0 /src/test/ui/mir/mir-typeck-normalize-fn-sig.rs
parentAdding debian version 1.67.1+dfsg1-1. (diff)
downloadrustc-64d98f8ee037282c35007b64c2649055c56af1db.tar.xz
rustc-64d98f8ee037282c35007b64c2649055c56af1db.zip
Merging upstream version 1.68.2+dfsg1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'src/test/ui/mir/mir-typeck-normalize-fn-sig.rs')
-rw-r--r--src/test/ui/mir/mir-typeck-normalize-fn-sig.rs30
1 files changed, 0 insertions, 30 deletions
diff --git a/src/test/ui/mir/mir-typeck-normalize-fn-sig.rs b/src/test/ui/mir/mir-typeck-normalize-fn-sig.rs
deleted file mode 100644
index bdd9321af..000000000
--- a/src/test/ui/mir/mir-typeck-normalize-fn-sig.rs
+++ /dev/null
@@ -1,30 +0,0 @@
-// run-pass
-#![allow(unused_variables)]
-// This code was creating an ICE in the MIR type checker. The reason
-// is that we are reifying a reference to a function (`foo::<'x>`),
-// which involves extracting its signature, but we were not
-// normalizing the signature afterwards. As a result, we sometimes got
-// errors around the `<u32 as Foo<'x>>::Value`, which can be
-// normalized to `f64`.
-
-#![allow(dead_code)]
-
-trait Foo<'x> {
- type Value;
-}
-
-impl<'x> Foo<'x> for u32 {
- type Value = f64;
-}
-
-struct Providers<'x> {
- foo: for<'y> fn(x: &'x u32, y: &'y u32) -> <u32 as Foo<'x>>::Value,
-}
-
-fn foo<'y, 'x: 'x>(x: &'x u32, y: &'y u32) -> <u32 as Foo<'x>>::Value {
- *x as f64
-}
-
-fn main() {
- Providers { foo };
-}