-
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
Add reference tracking for the result variable #2447
Conversation
I checked for other places where references are created internally but not tracked; Seems the only remaining ones are related to attachments. I'm not really sure which one of those actually needs to be tracked, etc. @dsainati1 Can you maybe have a look? Just look for the usages of |
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit 147e51e Collapsed results for better readability
|
Codecov Report
@@ Coverage Diff @@
## master #2447 +/- ##
=======================================
Coverage 78.31% 78.31%
=======================================
Files 325 325
Lines 72330 72342 +12
=======================================
+ Hits 56646 56658 +12
Misses 13606 13606
Partials 2078 2078
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Should this be merged into the
I took a look when I merged attachments into Stable Cadence. The only reference we need to track there is the references created via attachment access |
Reference tracking was already there in master/previous releases, but used for a different purpose: to keep the reference valid even after the resource is moved (i.e: to make it point to the correct resource instance). It was only re-purposed in Stable Cadence, to use it for invalidation.
Similar to the example here, wouldn't it be possible to store the reference to the base/self temporarily, and return the reference later (in the same execution), but after the refrenced resource (attachment) is moved? |
af7f97c
to
b743004
Compare
@turbolent @dsainati1 Can you have one final look, please? |
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.
Great work! Thank you for fixing all the cases 👍
Description
Follow-up on #2444.
master
branchFiles changed
in the Github PR explorer