Closed
Description
STR
fn main() {
S { x: 4,
y: 5 };
}
fn foo() {
Expected Result
An error message pointing to foo
Actual Result
Compiling playground v0.0.1 (/playground)
error: this file contains an un-closed delimiter
--> src/main.rs:5:12
|
2 | S { x: 4,
| - this delimiter might not be properly closed...
3 | y: 5 };
| - ...as it matches this but it has different indentation
4 | }
5 | fn foo() {
| - ^
| |
| un-closed delimiter
The heuristic feels incorrect to me - the delimiter on S
looks perfectly well-closed.
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
arielb1 commentedon Dec 15, 2018
One way to improve the heuristic would be to not treat delimiters where the closing delimiter is more indented than the opening delimiter as suspicious (i.e., a delimiter is suspicious if it is popped by a less indented delimiter). Are there any interesting false negatives that this causes?
arielb1 commentedon Dec 15, 2018
cc @estebank - this lint was introduced in #53949 & #54092.
Rollup merge of rust-lang#56910 - estebank:unclosed-eof, r=oli-obk
iamgabrielsoft commentedon Apr 1, 2022
I had the same issue, try closing all empty braces from your for loop, if statement and function statement.
very useful for me...