-
Notifications
You must be signed in to change notification settings - Fork 672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge 5.x #10504
Merged
Merged
Merge 5.x #10504
Conversation
This file contains 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
vimeo#10068 added isset restrictions that didn't consider null coalesces on match expressions. This restores that support by converting the match expression to a virtual variable for the isset analysis, similar to other incompatible expressions.
…ypes update define types to be correct
…andomization-of-tests use branch name to randomize tests to ensure test dependencies will error
vimeo#10385 "broke" this by propagating pseudo static methods from traits to using classes. `AtomicStaticCallAnalyzer` was then not capable of dealing with this, because now these static pseudo methods actually exist. As long as the methods from traits aren't actually transferred to the using class, it seems right that the logic in `AtomicStaticCallAnalyzer` uses `::getDeclaringMethodId()` instead of `::getAppearingMethodId()` for this purpose.
This can also return namespace nodes, which are not a child class of DOMNode.
Fix return type of DOMXPath::query
Fix CLI -r error
Use correct file path while adding unused suppressions for virtual __…
Restore support for null coalesce on match expressions
Fix static magic method pureness not being inherited from traits
Implement __set method in SimpleXMLElement stub
…e-specific Make getrandmax type more specific and unserialize to require class-string
…pe-failing-ci Fix mb_get_info can return null - CI failing bc of reflection
when max literal string length is 0, which means literal strings are disabled
…type-more-specific make basename & dirname return types more specific
…-assignments add support for extract to set variables for keyed arrays and respect EXTR_SKIP
…ry-separator-in-error-message remove redundat directory separator which caused "//" in path not found errors
…-non-empty-string-when-literal-strings-disabled Fix empty literal string becomes non-empty-string
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.
No description provided.