diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2018-12-16 14:08:16 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-16 14:08:16 +0100 |
| commit | 6ec6f487696eff39f5db68a9d612b899f7815f5e (patch) | |
| tree | 1c94644474b30624e8900c6b7e1eda8802b4f783 /src/libstd | |
| parent | cdadb72a3329ac1fb463106bbce32b642498fb50 (diff) | |
| parent | c0e3f4b8bbf10cc308823c98913b942b75c6a543 (diff) | |
| download | rust-6ec6f487696eff39f5db68a9d612b899f7815f5e.tar.gz rust-6ec6f487696eff39f5db68a9d612b899f7815f5e.zip | |
Rollup merge of #56439 - JohnGinger:master, r=nikomatsakis
Clearer error message for dead assign I'm not that this is the right place for this (if it needs an RFC or not). I had the problem where I misunderstood the compiler lint message https://github.com/rust-lang/rust/issues/56436 and other people seem to have had the same problem https://www.reddit.com/r/rust/comments/8cy9p4/value_assigned_to_is_never_read/. I think this new wording might be slightly clearer (and help out beginners like me). I'm very new though, so there might be some nuance I'm missing that would make this more confusing or a bad idea for other reasons. I thought I would create a PR to make it easy to change the code if the consensus was that it would make sense to make a change. If this is the wrong place for this sort of thing I'll happily delete/move it.
Diffstat (limited to 'src/libstd')
0 files changed, 0 insertions, 0 deletions
