Clarify forward_static_call() documentation#5681
Open
zonuexe wants to merge 1 commit into
Open
Conversation
zonuexe
force-pushed
the
clarify-forward-static-call-docs
branch
from
July 14, 2026 14:47
81e7e08 to
64c183f
Compare
lacatoire
approved these changes
Jul 15, 2026
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
2 participants
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.
The
forward_static_call()andforward_static_call_array()descriptions implied that these functions simply call static methods.This clarifies that they call a callback while preserving the current called class for method callbacks, making them useful for static method callbacks that should behave like forwarding calls such as
parent::orself::.The
forward_static_call_array()parameter note is also updated to matchcall_user_func_array(): parameters can be passed by reference when the corresponding element in theargsarray is a reference.I am not a native English speaker, so I do not have strong preferences about the exact wording or nuance.