blob: 3db59631ef8da3e9cdaaa979cd15d33c98922c73 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
// Tests that trait bounds on specializing trait impls must be `~const` if the
// same bound is present on the default impl and is `~const` there.
// check-pass
// FIXME(effects) ^ should error
#![feature(const_trait_impl)]
#![feature(rustc_attrs)]
#![feature(min_specialization)]
#[rustc_specialization_trait]
trait Specialize {}
#[const_trait]
trait Foo {}
#[const_trait]
trait Bar {
fn bar();
}
// bgr360: I was only able to exercise the code path that raises the
// "missing ~const qualifier" error by making this base impl non-const, even
// though that doesn't really make sense to do. As seen below, if the base impl
// is made const, rustc fails earlier with an overlapping impl failure.
impl<T> Bar for T
where
T: ~const Foo,
{
default fn bar() {}
}
impl<T> Bar for T
where
T: Foo, //FIXME ~ ERROR missing `~const` qualifier
T: Specialize,
{
fn bar() {}
}
#[const_trait]
trait Baz {
fn baz();
}
impl<T> const Baz for T
where
T: ~const Foo,
{
default fn baz() {}
}
impl<T> const Baz for T //FIXME ~ ERROR conflicting implementations of trait `Baz`
where
T: Foo,
T: Specialize,
{
fn baz() {}
}
fn main() {}
|
