Refine dclone definitions not to leak outside of REXML #37
Conversation
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
|
Thanks! |
abrom
added a commit
to abrom/rexml
that referenced
this pull request
May 19, 2021
ruby#37 fixes leakage of `dclone` method
Merged
hsbt
pushed a commit
that referenced
this pull request
May 19, 2021
#37 fixes leakage of `dclone` method
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While investigating my app, I found an unfamiliar
dclonemethod onObject, which turned out to be defined here inxpath_parser.rbonly for using inxpath_parser.rb.I believe this is the very use case of Ruby's most underevaluated feature, Refinements.
With this patch, we're no longer seeing the
dclonemethod leaking into our apps.