ForNeVeR / ForNeVeR/Cesium

Better parser error reporting

Open
#192 1 comment 0 reactions 0 assignees View on GitHub
area:parser kind:feature status:help-wanted
Dominant language
C#
Stars
451
Forks
49
Avg merge
13h 59m
Merged PRs (30d)
6

Description

```
int test() {
return 1;
}
int main(void) {
if (!test()) return -3;
return 0; }
```
Produces ` Excessive output after the end of a translation unit at line 5, column 10: KeywordInt int.`

If I comment out `if (!test()) return -3;` then things starts working.

Okay, I figure out while I wrote this, we lack of support for `!` operator for conditions, but I think we should do something about better user reporting.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.