Exit early in TrinaryLogic::lazyAnd() and lazyOr() if current instance allows it
#2173
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
|
Thank you! |
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.
In the scope of the lazy methods this makes sense to me. But this change won't affect PHPStan at all at the moment, because all
lazyAnd()andlazyOr()are called on validyesornoalready. It would lead to an early exit potentially if those methods would be used more dynamically like e.g.TrinaryLogic::createFromBoolean($expression)->lazyAnd(...)this is covered by already existing tests at least so far that tests would break if the logic is inverted.