-
-
Notifications
You must be signed in to change notification settings - Fork 932
1.4.9 #6782
ondrejmirtes
started this conversation in
General
1.4.9
#6782
-
Improvements 🔧
Identical(===and!==) andEqual(==and!=) with the same variables resolve toConstantBooleanType(phpstan/phpstan-src@98c4d84)- Scalars of the same type on both of
Equal(==and!=) are delegated toIdentical(===and!==) (phpstan/phpstan-src@316f269)
Bugfixes 🐛
- Fix trait detection recursion (#1050), Recursion Memory Bug when using Traits #6740 , thanks @herndlm!
- Do not add
nullto a template type for a default parameter valuenull(phpstan/phpstan-src@7a66cb6), Template loses null when set to null by default #6584 - Fix nullable closure parameter type (phpstan/phpstan-src@c05ba98), nullable parameters not honored on closures #6701
- TemplateType - fix description for subtracted mixed bound (phpstan/phpstan-src@6525d68)
- Fix dead catch when iterating objects (#1051), False Positive: Dead Catch for exceptions thrown from \Traversable or \Iterator traversing #5903 , thanks @rajyan!
- Fix false positive dead catch on property assignment (#1047), Deadcatch on property assignment #6256 , thanks @rajyan!
- Fix template type subtraction and union (phpstan/phpstan-src@51e2df3), Invalid "evaluates to false" with generics + inheritance #6591
- Simulate
offsetSetto get throw points for ArrayAccess assignment (#1054), ArrayAccess::offsetSet() may throw an exception #4852 , thanks @rajyan! - Make return type extension for
array_column()aware of PHP version (#1053), thanks @jlherren! - Fix Unused private constant with an indirect access (#1059), Incorrect unused reporting on private class const when called using $this::PRIVATE syntax #6758 , thanks @rajyan!
- Fix
Equal(==and!=) handling in TypeSpecifier (phpstan/phpstan-src@10b295f) - Fix more TypeSpecifier issues regarding
Identical(===and!==) (#1058)
This discussion was created from the release 1.4.9.
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment