Clarify forward_static_call docs - #5784
Open
zonuexe wants to merge 1 commit into
Open
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
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 PR replaces #5681 and has been rebased on the latest
masterafter 846dfb8.Commit 846dfb8 clarified that
forward_static_call_array()does not require an active class scope and behaves likecall_user_func_array()when called outside a class context.This PR keeps that correction and focuses on the remaining parts not covered by that commit:
forward_static_call()is not limited to calling static methods, but preserves the current called class for method callbacksstatic::resolves to the current called classparent::orself::forward_static_call_array()parameter note to matchcall_user_func_array(): parameters can be passed by reference when the corresponding element in theargsarray is a reference