diff options
| author | Barosl LEE <github@barosl.com> | 2015-01-21 02:16:45 +0900 |
|---|---|---|
| committer | Barosl LEE <github@barosl.com> | 2015-01-21 02:16:45 +0900 |
| commit | 1d8b91781189a1e859d4c7f73b153abb913a292c (patch) | |
| tree | caf856158366aa817667c8e1e71a740617f49fe5 /src/libstd | |
| parent | ffd8cb79a2d3da6629c8f54ef9ea9c29bd92fc9e (diff) | |
| parent | 6ab95bdd62095429139f1b24717cbf0e5aa4a235 (diff) | |
Rollup merge of #20998 - estsauver:20984, r=steveklabnik
There are a large number of places that incorrectly refer to deriving in comments, instead of derives. If someone could look at src/etc/generate-deriving-span-tests.py, I'm not sure how those tests were passing before/if they were.
Diffstat (limited to 'src/libstd')
| -rw-r--r-- | src/libstd/fmt.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/fmt.rs b/src/libstd/fmt.rs index 36afa0956d2..88fb983361a 100644 --- a/src/libstd/fmt.rs +++ b/src/libstd/fmt.rs @@ -221,7 +221,7 @@ //! - `fmt::Show` implementations should be implemented for **all** public types. //! Output will typically represent the internal state as faithfully as possible. //! The purpose of the `Show` trait is to facilitate debugging Rust code. In -//! most cases, using `#[deriving(Show)]` is sufficient and recommended. +//! most cases, using `#[derive(Show)]` is sufficient and recommended. //! //! Some examples of the output from both traits: //! |
