about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-10-19 12:11:13 -0700
committerbors <bors@rust-lang.org>2013-10-19 12:11:13 -0700
commit9d047cdead764ae33e19a7149286302560b000f2 (patch)
tree35bf6c0207547825afaac78e5dbdd5e63b92bec7
parent310f7a5f5260034c8186020409facaa54d430b88 (diff)
parent759b20da87b65d45b552adc75dd418e89b201261 (diff)
downloadrust-9d047cdead764ae33e19a7149286302560b000f2.tar.gz
rust-9d047cdead764ae33e19a7149286302560b000f2.zip
auto merge of #9952 : huonw/rust/fmt-doc, r=alexcrichton
Cf. the concern raised in https://github.com/mozilla/rust/pull/9938#issuecomment-26648696.
-rw-r--r--src/libstd/fmt/mod.rs28
1 files changed, 14 insertions, 14 deletions
diff --git a/src/libstd/fmt/mod.rs b/src/libstd/fmt/mod.rs
index 20fc44169d0..3223ca9a731 100644
--- a/src/libstd/fmt/mod.rs
+++ b/src/libstd/fmt/mod.rs
@@ -134,20 +134,20 @@ actually requesting that an argument ascribes to a particular trait. This allows
 multiple actual types to be formatted via `{:d}` (like `i8` as well as `int`).
 The current mapping of types to traits is:
 
-* `?` => Poly
-* `d` => Signed
-* `i` => Signed
-* `u` => Unsigned
-* `b` => Bool
-* `c` => Char
-* `o` => Octal
-* `x` => LowerHex
-* `X` => UpperHex
-* `s` => String
-* `p` => Pointer
-* `t` => Binary
-* `f` => Float
-* `` (nothing) => Default
+* `?` ⇒ `Poly`
+* `d` ⇒ `Signed`
+* `i` ⇒ `Signed`
+* `u` ⇒ `Unsigned`
+* `b` ⇒ `Bool`
+* `c` ⇒ `Char`
+* `o` ⇒ `Octal`
+* `x` ⇒ `LowerHex`
+* `X` ⇒ `UpperHex`
+* `s` ⇒ `String`
+* `p` ⇒ `Pointer`
+* `t` ⇒ `Binary`
+* `f` ⇒ `Float`
+* *nothing* ⇒ `Default`
 
 What this means is that any type of argument which implements the
 `std::fmt::Binary` trait can then be formatted with `{:t}`. Implementations are