diff options
| author | Zack M. Davis <code@zackmdavis.net> | 2016-06-12 20:55:36 -0700 |
|---|---|---|
| committer | Zack M. Davis <code@zackmdavis.net> | 2016-06-12 21:14:30 -0700 |
| commit | e4c566ccefacfac4f5883b1719e400c3a239c742 (patch) | |
| tree | 7c656559c31a7abee6368b11228defc3393e74cc /src/liballoc_system | |
| parent | c17f1a66f97ec26cdf746992f240aaf640c0fd20 (diff) | |
| download | rust-e4c566ccefacfac4f5883b1719e400c3a239c742.tar.gz rust-e4c566ccefacfac4f5883b1719e400c3a239c742.zip | |
edit E0453 long explanation for style, clarity, and citizenship
It turns out that the subsequent lines of the error message comment should be aligned like this. The "turns the corresponding compiler warning" language may not be strictly the most accurate—a lint check isn't the same as a compiler warning; it emits a compiler warning if it's set to the `warn` level— but it may be worth glossing over such distinctions in favor of simple, familar phrasings for the sake of pedagogy; thanks to Guillaume Gomez for the wording suggestion. Let's also fix up the introductory clauses of the sentences about how to fix the error to put a little more emphasis on the fact that the `forbid` setting was probably there for a reason.
Diffstat (limited to 'src/liballoc_system')
0 files changed, 0 insertions, 0 deletions
