Improve return types of explode() with limit#2286
Merged
muglug merged 1 commit intovimeo:masterfrom Nov 2, 2019
shira-374:improve-explode-handling
Merged
Improve return types of explode() with limit#2286muglug merged 1 commit intovimeo:masterfrom shira-374:improve-explode-handling
muglug merged 1 commit intovimeo:masterfrom
shira-374:improve-explode-handling
Conversation
Collaborator
|
Thanks! |
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.
Currently,
explode()calls with 3 arguments are skipped byFunctionAnalyzerand fallback to the defaultarray<int, string>|falsereturn type.https://psalm.dev/r/2fecda20b4
This PR aims to improve this by extending the existing rules by:
explode()with$limit>= 0 should always return a non-empty listexplode()with$limit< 0 (or dynamic) may return an empty list