respond_to?(<symbol>) => true optimization #8862
Draft
+232
−22
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
|
This could be expanded to make false results also constant by additionally checking if |
This optimizes the common case of respond_to? with a literal symbol. When the method is "naturally" respond_to? => true then that result can be cached behind the usual guards. This makes the success path essentially free. The logic here has a lot of copied behavior from elsewhere and utilizes some now-static methods from InvokeSite, so it could be refactored along with the rest of indy logic to be much simpler. There's a lot of duplicated code here from other call site forms, demonstrating the need for a refactor of all indy binding logic.
|
This needs some refactoring to work properly. I hack one fix in and break something else. On pause for the moment until I can get some time to rework indy call sites for more composability. |
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.
This optimizes the common case of respond_to? with a literal symbol. When the method is "naturally" respond_to? => true then that result can be cached behind the usual guards. This makes the success path essentially free.
The logic here has a lot of copied behavior from elsewhere and utilizes some now-static methods from InvokeSite, so it could be refactored along with the rest of indy logic to be much simpler.