Skip to content

Commit 7fc2e6e

Browse files
committed
Further improvements with spaces and ignore rust directive.
1 parent dffd656 commit 7fc2e6e

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

book/src/using-bitfields.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -18,16 +18,16 @@ void print_bitfield(bitfield bfield)
1818
1919
Bindgen creates a set of field getters and setters for interacting with the bitset. For example,
2020
21-
```rust
22-
let mut bfield = unsafe{ create_bitfield() };
21+
```rust,ignore
22+
let mut bfield = unsafe { create_bitfield() };
2323
2424
bfield.set_a(1);
2525
println!("a set to {}", bfield.a());
2626
bfield.set_b(1);
2727
println!("b set to {}", bfield.b());
2828
bfield.set_c(3);
2929
println!("c set to {}", bfield.c());
30-
unsafe{ print_bitfield(bfield) };
30+
unsafe { print_bitfield(bfield) };
3131
```
3232

3333
will print out
@@ -41,13 +41,13 @@ bitfield: a:1, b:1, c:3
4141

4242
Overflowing a bitfield will result in the same behavior as in C/C++: the bitfield will be set to 0.
4343

44-
```rust
45-
let mut bfield = unsafe{ create_bitfield() };
44+
```rust,ignore
45+
let mut bfield = unsafe { create_bitfield() };
4646
bfield.set_a(1);
4747
bfield.set_b(1);
4848
bfield.set_c(12);
4949
println!("c set to {} due to overflow", bfield.c());
50-
unsafe{ print_bitfield(bfield) };
50+
unsafe { print_bitfield(bfield) };
5151
```
5252

5353
will print out
@@ -59,11 +59,11 @@ bitfield: a:1, b:1, c:0
5959

6060
To create a new bitfield in Rust, use mem::zeroed.
6161

62-
```rust
62+
```rust,ignore
6363
let mut bfield = unsafe { mem::zeroed::<bitfield>() };
6464
bfield.set_a(1);
6565
bfield.set_c(2);
66-
unsafe{ print_bitfield(bfield) };
66+
unsafe { print_bitfield(bfield) };
6767
```
6868

6969
This will print out
@@ -110,26 +110,26 @@ void walk_bitfield() {
110110
}
111111
```
112112

113-
```rust
113+
```rust,ignore
114114
fn walk_bitfield() {
115115
let mut bfield = unsafe { mem::zeroed::<bitfield>() };
116-
unsafe{ print_bitfield(bfield) };
116+
unsafe { print_bitfield(bfield) };
117117
bfield.set_c(1);
118-
unsafe{ print_bitfield(bfield) };
118+
unsafe { print_bitfield(bfield) };
119119
bfield.set_c(2);
120-
unsafe{ print_bitfield(bfield) };
120+
unsafe { print_bitfield(bfield) };
121121
bfield.set_c(3);
122-
unsafe{ print_bitfield(bfield) };
122+
unsafe { print_bitfield(bfield) };
123123
bfield.set_c(4);
124-
unsafe{ print_bitfield(bfield) };
124+
unsafe { print_bitfield(bfield) };
125125
bfield.set_c(-1);
126-
unsafe{ print_bitfield(bfield) };
126+
unsafe { print_bitfield(bfield) };
127127
bfield.set_c(-2);
128-
unsafe{ print_bitfield(bfield) };
128+
unsafe { print_bitfield(bfield) };
129129
bfield.set_c(-3);
130-
unsafe{ print_bitfield(bfield) };
130+
unsafe { print_bitfield(bfield) };
131131
bfield.set_c(-4);
132-
unsafe{ print_bitfield(bfield) };
132+
unsafe { print_bitfield(bfield) };
133133
}
134134
```
135135

@@ -160,7 +160,7 @@ bitfield: a:0, b:0, c:0
160160

161161
However, Bindgen's getter provides different results:
162162

163-
```rust
163+
```rust,ignore
164164
fn getter_walk_bitfield() {
165165
let mut bfield = unsafe { mem::zeroed::<bitfield>() };
166166
println!("c set to {}", bfield.c());

0 commit comments

Comments
 (0)