-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't report errors for invalid types #1597
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add some tests that previously would have reported an invalid type error and now do not?
Codecov Report
@@ Coverage Diff @@
## master #1597 +/- ##
==========================================
- Coverage 74.74% 74.73% -0.01%
==========================================
Files 288 288
Lines 55340 55340
==========================================
- Hits 41362 41357 -5
- Misses 12486 12489 +3
- Partials 1492 1494 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit 1216be2 Results
|
Added tests in 1004a81 |
Description
While analyzing contracts I noticed several unnecessary error messages for invalid types, which are results for previous errors.
Just like everywhere else already, don't report errors for unexpected invalid types for:
Reported an error like
expected Bool, got <<invalid>>
if let nonOpt = opt { ... }
).Reported an error like
expected optional, got <<invalid>>
master
branchFiles changed
in the Github PR explorer