rust/tests/ui/drop/repeat-drop-2.rs

fn borrowck_catch() {
    let foo = String::new();
    let _bar = foo;
    let _baz = [foo; 0]; //~ ERROR use of moved value: `foo` [E0382]
}

const _: [String; 0] = [String::new(); 0];
//~^ ERROR destructor of `String` cannot be evaluated at compile-time [E0493]

fn must_be_init() {
    let x: u8;
    let _ = [x; 0]; //~ ERROR E0381
}

fn main() {}
Modify MIR building to drop `foo` in `[foo; 0]` 2022-04-13 06:08:58 -05:00			`fn borrowck_catch() {`
			`let foo = String::new();`
			`let _bar = foo;`
			let _baz = [foo; 0]; //~ ERROR use of moved value: `foo` [E0382]
			`}`

			`const _: [String; 0] = [String::new(); 0];`
Note the type when unable to drop values in compile time 2022-09-23 09:22:36 -05:00			//~^ ERROR destructor of `String` cannot be evaluated at compile-time [E0493]
Modify MIR building to drop `foo` in `[foo; 0]` 2022-04-13 06:08:58 -05:00
			`fn must_be_init() {`
			`let x: u8;`
On partial uninit error point at where we need init When a binding is declared without a value, borrowck verifies that all codepaths have one assignment to them to initialize them fully. If there are any cases where a condition can be met that leaves the binding uninitialized or we attempt to initialize a field of an unitialized binding, we emit E0381. We now look at all the statements that initialize the binding, and use them to explore branching code paths that don't and point at them. If we find no potential places where an assignment to the binding might be missing, we display the spans of all the existing initializers to provide some context. 2022-06-21 13:57:45 -05:00			`let _ = [x; 0]; //~ ERROR E0381`
Modify MIR building to drop `foo` in `[foo; 0]` 2022-04-13 06:08:58 -05:00			`}`

			`fn main() {}`