about summary refs log tree commit diff
path: root/src/liballoc
diff options
context:
space:
mode:
authorkennytm <kennytm@gmail.com>2018-10-18 10:47:23 +0800
committerkennytm <kennytm@gmail.com>2018-10-18 12:54:54 +0800
commit7538c625016065f13506bc7b5ef5a76fb2d4ede3 (patch)
tree1185766bb25bc8713b06f933ccf94c65ac9e394f /src/liballoc
parent617faa90e5bfd02862681fe29f3bfd24b567a16f (diff)
parent91f57787c0a46b7e6f9ae19ed7249498b564fbf1 (diff)
downloadrust-7538c625016065f13506bc7b5ef5a76fb2d4ede3.tar.gz
rust-7538c625016065f13506bc7b5ef5a76fb2d4ede3.zip
Rollup merge of #55050 - tshepang:repetition, r=steveklabnik
doc std::fmt: the Python inspiration is already mentioned in precedin…

…g paragraph
Diffstat (limited to 'src/liballoc')
-rw-r--r--src/liballoc/fmt.rs3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/liballoc/fmt.rs b/src/liballoc/fmt.rs
index a2e68a223f1..b857964ccb3 100644
--- a/src/liballoc/fmt.rs
+++ b/src/liballoc/fmt.rs
@@ -335,8 +335,7 @@
 //!
 //! Each argument being formatted can be transformed by a number of formatting
 //! parameters (corresponding to `format_spec` in the syntax above). These
-//! parameters affect the string representation of what's being formatted. This
-//! syntax draws heavily from Python's, so it may seem a bit familiar.
+//! parameters affect the string representation of what's being formatted.
 //!
 //! ## Fill/Alignment
 //!