Conversation
VincentLanglet
requested changes
Oct 3, 2026
VincentLanglet
left a comment
Contributor
There was a problem hiding this comment.
I don't think your example is valid because if I call
Replacer::replace() I'll expect that the call is pure, which is invalid with your implementation.
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.
Found while working on #6667.
FunctionPurityCheckchecked the body of a method for purity whenever it had a@pure-unless-callable-is-impureor@pure-unless-parameter-passedtag, even when the method itself is marked@phpstan-impureand only inherits the tag:The method declares itself impure, so PHPStan shouldn't call it a pure method or report its side effects. With bleeding edge,
MethodSignatureRulereports the override itself asmethod.impureOverridePureUnlessParameterPassedormethod.impureOverridePureUnlessCallable.Changes
FunctionPurityCheck::check()checks the body against the conditional purity only when the method is not marked impure. A method marked@phpstan-impuregoes through the existing impure branch, so one without any side effects getsimpureMethod.purelike any other.