-
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
Fix definite field initialization analysis #1424
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1424 +/- ##
==========================================
- Coverage 73.14% 73.12% -0.02%
==========================================
Files 282 282
Lines 39067 39065 -2
==========================================
- Hits 28574 28568 -6
- Misses 9050 9052 +2
- Partials 1443 1445 +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 8129778 Results
|
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.
Nice work! 👏 Glad it was an easy fix, I couldn't quite see it 🙂
Co-authored-by: Bastian Müller <[email protected]>
Closes #1405
Description
MaybeJumpedOrReturned
(nowMaybeReturned
) was used only to determine whether a branch of the function has a 'return'. Marking it astrue
for jumps (break
andcontinue
statements) was going against the above assumption/usage.Reverted the change of using that flag for both jumps and returns, and continue to use it for returns only.
master
branchFiles changed
in the Github PR explorer