rust/tests/ui/traits/cycle-generic-bound.rs

// run-pass
// Regression test for #15477. This test just needs to compile.

// pretty-expanded FIXME #23616

trait Chromosome<X: Chromosome<i32>> {
}

impl Chromosome<i32> for i32 { }

fn main() { }
tests: Add missing run-pass annotations 2019-07-26 16:54:25 -05:00			`// run-pass`
Rework trait-bound-conversion so be based on the AST and rework collect to pass in the appropriate ast::generics etc 2015-02-18 09:39:39 -06:00			`// Regression test for #15477. This test just needs to compile.`
Comprehence cycle detection in `collect`. In some cases, the cycles we report are not necessary cycles, but we'll work on refactoring them over time. This overlaps with the cycle detection that astconv already does: I left that code in because it gives a more targeted error message, though perhaps less helpful in that it doesn't give the full details of the cycle. 2015-02-17 16:11:01 -06:00
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05:00			`// pretty-expanded FIXME #23616`

Fallout in tests 2015-03-31 18:58:01 -05:00			`trait Chromosome<X: Chromosome<i32>> {`
Comprehence cycle detection in `collect`. In some cases, the cycles we report are not necessary cycles, but we'll work on refactoring them over time. This overlaps with the cycle detection that astconv already does: I left that code in because it gives a more targeted error message, though perhaps less helpful in that it doesn't give the full details of the cycle. 2015-02-17 16:11:01 -06:00			`}`

Make RFC 1214 warnings into errors, and rip out the "warn or err" associated machinery. Future such attempts should go through lints anyhow. There is a fair amount of fallout in the compile-fail tests, as WF checking now occurs earlier in the process. 2015-12-15 03:31:58 -06:00			`impl Chromosome<i32> for i32 { }`

Comprehence cycle detection in `collect`. In some cases, the cycles we report are not necessary cycles, but we'll work on refactoring them over time. This overlaps with the cycle detection that astconv already does: I left that code in because it gives a more targeted error message, though perhaps less helpful in that it doesn't give the full details of the cycle. 2015-02-17 16:11:01 -06:00			`fn main() { }`