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

// check-pass
#![allow(dead_code)]
#![allow(non_camel_case_types)]

// Testing that the B's are resolved


trait clam<A> { fn get(self) -> A; }

struct foo(isize);

impl foo {
    pub fn bar<B,C:clam<B>>(&self, _c: C) -> B { panic!(); }
}

pub fn main() { }
Use check-pass in ui tests where appropriate 2019-11-04 00:00:00 +00:00			`// check-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 23:51:35 +02:00			`#![allow(dead_code)]`
Add `#![allow(..)]` for a slew of lints of migrated run-pass tests, to silence stderr output. 2018-08-31 15:02:01 +02:00			`#![allow(non_camel_case_types)]`

Add a test for issue #2312 2012-08-06 11:08:52 -07:00			`// Testing that the B's are resolved`

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 13:13:15 -07:00
Fallout: tests. As tests frequently elide things, lots of changes here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test. 2015-02-12 10:29:52 -05:00			`trait clam<A> { fn get(self) -> A; }`
Add a test for issue #2312 2012-08-06 11:08:52 -07:00
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`struct foo(isize);`
Add a test for issue #2312 2012-08-06 11:08:52 -07:00
Remove all uses of `pub impl`. rs=style 2013-05-31 15:17:22 -07:00			`impl foo {`
Rename fail! to panic! https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . \| xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-09 15:17:22 -04:00			`pub fn bar<B,C:clam<B>>(&self, _c: C) -> B { panic!(); }`
Add a test for issue #2312 2012-08-06 11:08:52 -07:00			`}`

check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() { }`