Merging upstream version 1.68.2+dfsg1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 0 insertions, 30 deletions

diff --git a/src/test/ui/const-generics/const-param-elided-lifetime.rs b/src/test/ui/const-generics/const-param-elided-lifetime.rs
deleted file mode 100644
index 487b82dbf..000000000
--- a/src/test/ui/const-generics/const-param-elided-lifetime.rs
+++ /dev/null
@@ -1,30 +0,0 @@
-// Elided lifetimes within the type of a const generic parameters is disallowed. This matches the
-// behaviour of trait bounds where `fn foo<T: Ord<&u8>>() {}` is illegal. Though we could change
-// elided lifetimes within the type of a const generic parameters to be 'static, like elided
-// lifetimes within const/static items.
-// revisions: full min
-#![cfg_attr(full, feature(adt_const_params))]
-#![cfg_attr(full, allow(incomplete_features))]
-
-struct A<const N: &u8>;
-//~^ ERROR `&` without an explicit lifetime name cannot be used here
-//[min]~^^ ERROR `&'static u8` is forbidden
-trait B {}
-
-impl<const N: &u8> A<N> {
-//~^ ERROR `&` without an explicit lifetime name cannot be used here
-//[min]~^^ ERROR `&'static u8` is forbidden
-    fn foo<const M: &u8>(&self) {}
-    //~^ ERROR `&` without an explicit lifetime name cannot be used here
-    //[min]~^^ ERROR `&'static u8` is forbidden
-}
-
-impl<const N: &u8> B for A<N> {}
-//~^ ERROR `&` without an explicit lifetime name cannot be used here
-//[min]~^^ ERROR `&'static u8` is forbidden
-
-fn bar<const N: &u8>() {}
-//~^ ERROR `&` without an explicit lifetime name cannot be used here
-//[min]~^^ ERROR `&'static u8` is forbidden
-
-fn main() {}