Remove redundant sections on bit validity

Author: chorman0773

src/types/boolean.md

@@ -127,14 +127,6 @@ r[type.bool.expr.cmp.less]
 r[type.bool.expr.cmp.less-eq]
 * `a <= b` is the same as `a == b | a < b`
 
-## Bit validity
-
-r[type.bool.validity]
-
-The single byte of a `bool` is guaranteed to be initialized (in other words,
-`transmute::<bool, u8>(...)` is always sound -- but since some bit patterns
-are invalid `bool`s, the inverse is not always sound).
-
 [boolean logic]: https://en.wikipedia.org/wiki/Boolean_algebra
 [enumerated type]: enum.md
 [expressions]: ../expressions.md

src/types/numeric.md

@@ -59,13 +59,6 @@ r[type.numeric.int.size.minimum]
 > pointer support is limited and may require explicit care and acknowledgment
 > from a library to support.
 
-## Bit validity
-
-r[type.numeric.validity]
-
-For every numeric type, `T`, the bit validity of `T` is equivalent to the bit
-validity of `[u8; size_of::<T>()]`. An uninitialized byte is not a valid `u8`.
-
 ## Representation
 
 r[type.numeric.repr]

src/types/textual.md

@@ -29,18 +29,6 @@ r[type.text.str-unsized]
 Since `str` is a [dynamically sized type], it can only be instantiated through a
 pointer type, such as `&str`.
 
-## Layout and bit validity
-
-r[type.text.layout]
-
-r[type.layout.char-layout]
-`char` is guaranteed to have the same size and alignment as `u32` on all platforms.
-
-r[type.layout.char-validity]
-Every byte of a `char` is guaranteed to be initialized (in other words,
-`transmute::<char, [u8; size_of::<char>()]>(...)` is always sound -- but since
-some bit patterns are invalid `char`s, the inverse is not always sound).
-
 [Unicode scalar value]: http://www.unicode.org/glossary/#unicode_scalar_value
 [undefined behavior]: ../behavior-considered-undefined.md
 [dynamically sized type]: ../dynamically-sized-types.md