diff options
author | Yuki Okushi <jtitor@2k36.org> | 2023-05-07 14:12:16 +0900 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-05-07 14:12:16 +0900 |
commit | 88a0204fcb6608862834f8b2c898168881fd3b9e (patch) | |
tree | 22553152ecb89dd83731eaf620ccaa9b28f965eb /tests/rustdoc-js-std/parser-errors.js | |
parent | 4e4e5bf17d6f7ed6876b4172a634d61c86e02e8c (diff) | |
parent | faa797e7e7bd75fd7dfd5a08fe8cf7bf82e02fd8 (diff) | |
download | rust-88a0204fcb6608862834f8b2c898168881fd3b9e.tar.gz |
Rollup merge of #111300 - Flying-Toast:while_true_span_condition, r=compiler-errors
Emit while_true lint spanning the entire loop condition
The lint that suggests `loop {}` instead of `while true {}` has functionality to 'pierce' parenthesis in cases like `while (true) {}`. In these cases, the emitted span only went to the hi of the `true` itself, not spanning the entire loop condition.
Before:
```
warning: denote infinite loops with `loop { ... }`
--> /tmp/foobar.rs:2:5
|
2 | while ((((((true)))))) {}
| ^^^^^^^^^^^^^^^^ help: use `loop`
|
= note: `#[warn(while_true)]` on by default
```
After:
```
warning: denote infinite loops with `loop { ... }`
--> /tmp/foobar.rs:2:5
|
2 | while ((((((true)))))) {}
| ^^^^^^^^^^^^^^^^^^^^^^ help: use `loop`
|
= note: `#[warn(while_true)]` on by default
```
This is especially a problem for rustfix.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions