diff options
author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-06 13:30:05 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-05-06 13:30:05 +0200 |
commit | 83b29ec743924dc3944ca2a50312ecbdef153588 (patch) | |
tree | 59bc999624850ac253e5509569a422153dc24023 /tests/rustdoc-js-std/parser-errors.js | |
parent | f440999bb2a894eee5f8a9d299ddb849420bcf63 (diff) | |
parent | a183ac6f90dc43a550a8afa5c01fdc797cf3d1d4 (diff) | |
download | rust-83b29ec743924dc3944ca2a50312ecbdef153588.tar.gz |
Rollup merge of #111230 - zacklukem:eq-less-to-less-eq, r=compiler-errors
add hint for =< as <=
Adds a compiler hint for when `=<` is typed instead of `<=`
Example hint:
```rust
fn foo() {
if 1 =< 3 {
println!("Hello, World!");
}
}
```
```
error: expected type, found `3`
--> main.rs:2:13
|
2 | if 1 =< 3 {
| -- ^ expected type
| |
| help: did you mean: `<=`
```
This PR only emits the suggestion if there is no space between the `=` and `<`. This hopefully narrows the scope of when this error is emitted, however this still allows this error to be emitted in cases such as this:
```
error: expected expression, found `;`
--> main.rs:2:18
|
2 | if 1 =< [i32;; 3]>::hello() {
| -- ^ expected expression
| |
| help: did you mean: `<=`
```
Which could be a good reason not to merge since I haven't been able to think of any other ways of narrowing the scope of this diagnostic.
closes #111128
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions