Skip to content

Commit ecb485a

Browse files
committed
Word wrapping in types chapter
1 parent 3991cf4 commit ecb485a

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

src/types.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -93,8 +93,8 @@ Tuple types and values are denoted by listing the types or values of their
9393
elements, respectively, in a parenthesized, comma-separated list.
9494

9595
Because tuple elements don't have a name, they can only be accessed by
96-
pattern-matching or by using `N` directly as a field to access the
97-
`N`th element.
96+
pattern-matching or by using `N` directly as a field to access the `N`th
97+
element.
9898

9999
An example of a tuple type and its use:
100100

@@ -162,13 +162,13 @@ expression](expressions.html#struct-expressions).
162162

163163
The memory layout of a `struct` is undefined by default to allow for compiler
164164
optimizations like field reordering, but it can be fixed with the
165-
`#[repr(...)]` attribute. In either case, fields may be given in any order in
166-
a corresponding struct *expression*; the resulting `struct` value will always
165+
`#[repr(...)]` attribute. In either case, fields may be given in any order in a
166+
corresponding struct *expression*; the resulting `struct` value will always
167167
have the same memory layout.
168168

169169
The fields of a `struct` may be qualified by [visibility
170-
modifiers](visibility-and-privacy.html), to allow access to data in a
171-
struct outside a module.
170+
modifiers](visibility-and-privacy.html), to allow access to data in a struct
171+
outside a module.
172172

173173
A _tuple struct_ type is just like a struct type, except that the fields are
174174
anonymous.
@@ -386,9 +386,9 @@ more of the closure traits:
386386
moved in the body of the closure. `Fn` inherits from `FnMut`, which itself
387387
inherits from `FnOnce`.
388388

389-
Closures that don't use anything from their environment ("non capturing closures")
390-
can be coerced to function pointers (`fn`) with the matching signature.
391-
To adopt the example from the section above:
389+
Closures that don't use anything from their environment ("non capturing
390+
closures") can be coerced to function pointers (`fn`) with the matching
391+
signature. To adopt the example from the section above:
392392

393393
```rust
394394
let add = |x, y| x + y;

0 commit comments

Comments
 (0)