@@ -284,8 +284,8 @@ extern "rust-intrinsic" {
284
284
///
285
285
/// `transmute` is semantically equivalent to a bitwise move of one type
286
286
/// into another. It copies the bits from the destination type into the
287
- /// source type, then forgets the original. If you know C or C++, it 's like
288
- /// `memcpy` under the hood.
287
+ /// source type, then forgets the original. It's equivalent to C 's `memcpy`
288
+ /// under the hood, just like `transmute_copy` .
289
289
///
290
290
/// `transmute` is incredibly unsafe. There are a vast number of ways to
291
291
/// cause undefined behavior with this function. `transmute` should be
@@ -299,7 +299,7 @@ extern "rust-intrinsic" {
299
299
/// There are a few things that `transmute` is really useful for.
300
300
///
301
301
/// Getting the bitpattern of a floating point type (or, more generally,
302
- /// type punning, when T and U aren't pointers):
302
+ /// type punning, when `T` and `U` aren't pointers):
303
303
///
304
304
/// ```
305
305
/// let bitpattern = unsafe {
@@ -339,11 +339,10 @@ extern "rust-intrinsic" {
339
339
/// # Alternatives
340
340
///
341
341
/// However, many uses of `transmute` can be achieved through other means.
342
- /// `transmute` can transform
343
- /// any type into any other, with just the caveat that they're the same
344
- /// size, and it sometimes results in interesting results. Below are common
345
- /// applications of `transmute` which can be replaced with safe applications
346
- /// of `as`:
342
+ /// `transmute` can transform any type into any other, with just the caveat
343
+ /// that they're the same size, and often interesting results occur. Below
344
+ /// are common applications of `transmute` which can be replaced with safe
345
+ /// applications of `as`:
347
346
///
348
347
/// Turning a pointer into a `usize`:
349
348
///
0 commit comments