@@ -132,7 +132,6 @@ pub use intrinsics::transmute;
132
132
/// [uninit]: fn.uninitialized.html
133
133
/// [clone]: ../clone/trait.Clone.html
134
134
/// [swap]: fn.swap.html
135
- /// [FFI]: ../../book/first-edition/ffi.html
136
135
/// [box]: ../../std/boxed/struct.Box.html
137
136
/// [leak]: ../../std/boxed/struct.Box.html#method.leak
138
137
/// [into_raw]: ../../std/boxed/struct.Box.html#method.into_raw
@@ -475,7 +474,7 @@ pub fn needs_drop<T>() -> bool {
475
474
///
476
475
/// This has the same effect as allocating space with
477
476
/// [`mem::uninitialized`][uninit] and then zeroing it out. It is useful for
478
- /// [ FFI] sometimes, but should generally be avoided.
477
+ /// FFI sometimes, but should generally be avoided.
479
478
///
480
479
/// There is no guarantee that an all-zero byte-pattern represents a valid value of
481
480
/// some type `T`. If `T` has a destructor and the value is destroyed (due to
@@ -486,7 +485,6 @@ pub fn needs_drop<T>() -> bool {
486
485
/// many of the same caveats.
487
486
///
488
487
/// [uninit]: fn.uninitialized.html
489
- /// [FFI]: ../../book/first-edition/ffi.html
490
488
/// [ub]: ../../reference/behavior-considered-undefined.html
491
489
///
492
490
/// # Examples
@@ -510,11 +508,9 @@ pub unsafe fn zeroed<T>() -> T {
510
508
/// **This is incredibly dangerous and should not be done lightly. Deeply
511
509
/// consider initializing your memory with a default value instead.**
512
510
///
513
- /// This is useful for [ FFI] functions and initializing arrays sometimes,
511
+ /// This is useful for FFI functions and initializing arrays sometimes,
514
512
/// but should generally be avoided.
515
513
///
516
- /// [FFI]: ../../book/first-edition/ffi.html
517
- ///
518
514
/// # Undefined behavior
519
515
///
520
516
/// It is [undefined behavior][ub] to read uninitialized memory, even just an
@@ -685,10 +681,9 @@ pub fn replace<T>(dest: &mut T, mut src: T) -> T {
685
681
/// While this does call the argument's implementation of [`Drop`][drop],
686
682
/// it will not release any borrows, as borrows are based on lexical scope.
687
683
///
688
- /// This effectively does nothing for
689
- /// [types which implement `Copy`](../../book/first-edition/ownership.html#copy-types),
690
- /// e.g. integers. Such values are copied and _then_ moved into the function,
691
- /// so the value persists after this function call.
684
+ /// This effectively does nothing for types which implement `Copy`, e.g.
685
+ /// integers. Such values are copied and _then_ moved into the function, so the
686
+ /// value persists after this function call.
692
687
///
693
688
/// This function is not magic; it is literally defined as
694
689
///
0 commit comments