Fix new
in subclasses of abstract classes when tap
is redeclared
#7536
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.
Motivation
I have an abstract class that happened to redeclare the
tap
method to be something else entirely. This used to work until 544f173. Sorbet seems to generally work around tampering like this (seeObject.instance_method(:method)
a few lines prior) so I reckon the same should happen here.I could have done:
but the code-readability benefits from
tap
are largely lost so it's IMO clearer to just avoid it entirely.Test plan
See included test.