-
Notifications
You must be signed in to change notification settings - Fork 462
Fix incorrect method visibility when merging with existing store cache #1736
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
Open
4lllex
wants to merge
1
commit into
ruby:master
Choose a base branch
from
4lllex:fix-visibility-merge
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+9
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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 catch on the root cause -
mergeis definitely reusing a stale@visibilityleft over frommarshal_load.I'd suggest fixing this one level down instead. Visibility is lexical state, and
Parser::Rubyalready tracks it separately in its own@visibility- it never touchesContext#visibility. Soadd_methodoverwritingmethod.visibilitywith the container's@visibilityis a leftover from the old design, and every caller passing in an already-complete method has to work around it:marshal_loadsets@visibilityjust soadd_methodpicks it upmerge(this bug) inherits whatmarshal_loadleft behindprepare_to_embedassignsself.visibility = code_object.visibilityback ontothe container, with a comment explaining the workaround
Parser::Rubyorders its calls carefully:a.visibility = visibility # should set after adding to containerDropping the assignment in
add_method(and the matching one inadd_attribute) fixes this at the root and lets all four workarounds go away.No new argument needed -
AnyMethodalready defaults to:publicand every caller sets visibility itself, somarshal_loadjust doesmethod.visibility = visibilitydirectly.