diff options
| author | bors <bors@rust-lang.org> | 2022-05-03 20:42:35 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-05-03 20:42:35 +0000 |
| commit | a10fe902d2c7afe3d42e9b00627a6983488521d3 (patch) | |
| tree | 8cb315c0df07395438dd0b7ef76a20f93fdde317 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 38b7a041cc8b346927b74edd8c7ddccee47a4c93 (diff) | |
| parent | 7017eb102d71526205b2feded779ff1f26d11da1 (diff) | |
| download | rust-a10fe902d2c7afe3d42e9b00627a6983488521d3.tar.gz rust-a10fe902d2c7afe3d42e9b00627a6983488521d3.zip | |
Auto merge of #8779 - binggh:easier-needless-late-init, r=llogiq
Easier readability for `needless_late_init` message Closes #8530 Updated the lint to use a `MultiSpan`, showing where the `let` statement was first used and where the initialisation statement was done, as in the format described, for easier readability. Was wondering why, when pushing the span label for the initialisation statement, that sometimes the prior statement above the initialisation statement gets pulled into the output as well - any insight is appreciated! --- changelog: [`needless_late_init`]: Now shows the `let` statement where it was first initialized
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions