diff options
| author | Chris Gregory <czipperz@gmail.com> | 2019-04-13 10:38:06 -0500 |
|---|---|---|
| committer | Chris Gregory <czipperz@gmail.com> | 2019-04-13 10:38:06 -0500 |
| commit | b701d32ca80e58d41cadc18755567794d5e65bd9 (patch) | |
| tree | aa44243850af3db281885c96665883a69c5651f1 | |
| parent | 6bf94cd3ff4af69c8128fb64d28a60f6c9385c19 (diff) | |
| download | rust-b701d32ca80e58d41cadc18755567794d5e65bd9.tar.gz rust-b701d32ca80e58d41cadc18755567794d5e65bd9.zip | |
Remove broken links to self in Into documentation
| -rw-r--r-- | src/libcore/convert.rs | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/libcore/convert.rs b/src/libcore/convert.rs index e981001bd64..2498159edc7 100644 --- a/src/libcore/convert.rs +++ b/src/libcore/convert.rs @@ -203,9 +203,9 @@ pub trait AsMut<T: ?Sized> { /// A value-to-value conversion that consumes the input value. The /// opposite of [`From`]. /// -/// One should only implement [`Into`] if a conversion to a type outside the current crate is -/// required. Otherwise one should always prefer implementing [`From`] over [`Into`] because -/// implementing [`From`] automatically provides one with a implementation of [`Into`] thanks to +/// One should only implement `Into` if a conversion to a type outside the current crate is +/// required. Otherwise one should always prefer implementing [`From`] over `Into` because +/// implementing [`From`] automatically provides one with a implementation of `Into` thanks to /// the blanket implementation in the standard library. [`From`] cannot do these type of /// conversions because of Rust's orphaning rules. /// @@ -214,7 +214,7 @@ pub trait AsMut<T: ?Sized> { /// # Generic Implementations /// /// - [`From`]`<T> for U` implies `Into<U> for T` -/// - [`Into`] is reflexive, which means that `Into<T> for T` is implemented +/// - `Into` is reflexive, which means that `Into<T> for T` is implemented /// /// # Implementing `Into` for conversions to external types /// |
