rust/tests/ui/borrow-by-val-method-receiver.rs

// run-pass

trait Foo {
    fn foo(self);
}

impl<'a> Foo for &'a [isize] {
    fn foo(self) {}
}

pub fn main() {
    let items = vec![ 3, 5, 1, 2, 4 ];
    items.foo();
}
tests: Add missing run-pass annotations 2019-07-26 16:54:25 -05:00			`// run-pass`

rustc: Fix an LLVM assertion that tripped when borrowing a by-val method receiver. In certain lvalue code paths, the type of the borrowed value was not being used to generate temporary spills. I'm a bit surprised we didn't hit this sooner. 2012-09-03 17:56:57 -05:00			`trait Foo {`
			`fn foo(self);`
			`}`

Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`impl<'a> Foo for &'a [isize] {`
rustc: Fix an LLVM assertion that tripped when borrowing a by-val method receiver. In certain lvalue code paths, the type of the borrowed value was not being used to generate temporary spills. I'm a bit surprised we didn't hit this sooner. 2012-09-03 17:56:57 -05:00			`fn foo(self) {}`
			`}`

check-fast fallout from removing export, r=burningtree 2013-02-01 21:43:17 -06:00			`pub fn main() {`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 16:54:04 -05:00			`let items = vec![ 3, 5, 1, 2, 4 ];`
cleanup: s/`v.slice*()`/`&v[a..b]`/g + remove redundant `as_slice()` calls 2015-01-26 20:21:15 -06:00			`items.foo();`
rustc: Fix an LLVM assertion that tripped when borrowing a by-val method receiver. In certain lvalue code paths, the type of the borrowed value was not being used to generate temporary spills. I'm a bit surprised we didn't hit this sooner. 2012-09-03 17:56:57 -05:00			`}`