rust/tests/ui/issues/issue-29857.rs

// check-pass

use std::marker::PhantomData;

pub trait Foo<P> {}

impl <P, T: Foo<P>> Foo<P> for Option<T> {}

pub struct Qux<T> (PhantomData<*mut T>);

impl<T> Foo<*mut T> for Option<Qux<T>> {}

pub trait Bar {
    type Output: 'static;
}

impl<T: 'static, W: Bar<Output = T>> Foo<*mut T> for W {}

fn main() {}
compiletest: Remove `skip-codegen` 2019-06-12 15:18:32 +00:00			`// check-pass`
Change error scheme so that if projection fails we generate `A::B` instead of `TyError` 2016-01-07 18:51:16 +00:00
Make coherence more tolerant of error types. Fixes #29857. Fixes #30589. 2016-01-02 09:57:55 +00:00			`use std::marker::PhantomData;`

			`pub trait Foo<P> {}`

Change error scheme so that if projection fails we generate `A::B` instead of `TyError` 2016-01-07 18:51:16 +00:00			`impl <P, T: Foo<P>> Foo<P> for Option<T> {}`
Make coherence more tolerant of error types. Fixes #29857. Fixes #30589. 2016-01-02 09:57:55 +00:00
			`pub struct Qux<T> (PhantomData<*mut T>);`

			`impl<T> Foo<*mut T> for Option<Qux<T>> {}`

			`pub trait Bar {`
			`type Output: 'static;`
			`}`

			`impl<T: 'static, W: Bar<Output = T>> Foo<*mut T> for W {}`

Removed `#[rustc_error]` from tests that are all `// compile-pass`. I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.) 2018-10-31 12:08:01 +00:00			`fn main() {}`