Re-enable GC of RGFs which haven't been drop_expr()
d
#63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revert some of #62
Originally GC of RGFs was implemented because people seemed to need it. So dropping support for this completely doesn't seem great.
Instead, this PR lets normal RGF bodies be GC'd as always. But if one calls
drop_expr
, we upgrade theWeakRef
to a normal strong reference in the cache, preventing the body from being GC'd thereafter.