Skip to content

Commit dba548d

Browse files
committed
fix via mdinger
1 parent 04578f6 commit dba548d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/doc/tarpl/repr-rust.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ struct FooRepr {
109109

110110
And indeed this is approximately how it would be laid out in general
111111
(modulo the size and position of `tag`). However there are several cases where
112-
such a representation is ineffiecient. The classic case of this is Rust's
112+
such a representation is inefficient. The classic case of this is Rust's
113113
"null pointer optimization". Given a pointer that is known to not be null
114114
(e.g. `&u32`), an enum can *store* a discriminant bit *inside* the pointer
115115
by using null as a special value. The net result is that
@@ -121,4 +121,4 @@ nested enums pooling their tags into a single descriminant, as they are by
121121
definition known to have a limited range of valid values. In principle enums can
122122
use fairly elaborate algorithms to cache bits throughout nested types with
123123
special constrained representations. As such it is *especially* desirable that
124-
we leave enum layout unspecified today.
124+
we leave enum layout unspecified today.

0 commit comments

Comments
 (0)