ignore various sample tests
This commit is contained in:
parent
bce808f911
commit
c749bb2272
|
|
@ -17,7 +17,7 @@ to that set; moving from a local variable removes it from that set.
|
||||||
|
|
||||||
Consider this example:
|
Consider this example:
|
||||||
|
|
||||||
```rust
|
```rust,ignore
|
||||||
fn foo() {
|
fn foo() {
|
||||||
let a: Vec<u32>;
|
let a: Vec<u32>;
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -4,7 +4,7 @@ In reality, it's not enough to track initialization at the granularity
|
||||||
of local variables. Rust also allows us to do moves and initialization
|
of local variables. Rust also allows us to do moves and initialization
|
||||||
at the field granularity:
|
at the field granularity:
|
||||||
|
|
||||||
```rust
|
```rust,ignore
|
||||||
fn foo() {
|
fn foo() {
|
||||||
let a: (Vec<u32>, Vec<u32>) = (vec![22], vec![44]);
|
let a: (Vec<u32>, Vec<u32>) = (vec![22], vec![44]);
|
||||||
|
|
||||||
|
|
@ -41,7 +41,7 @@ the [`move_paths` field of the `MoveData`][move_paths]. For example,
|
||||||
to convert a [`MovePathIndex`] `mpi` into a MIR [`Place`], you might
|
to convert a [`MovePathIndex`] `mpi` into a MIR [`Place`], you might
|
||||||
access the [`MovePath::place`] field like so:
|
access the [`MovePath::place`] field like so:
|
||||||
|
|
||||||
```rust
|
```rust,ignore
|
||||||
move_data.move_paths[mpi].place
|
move_data.move_paths[mpi].place
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue