Loss of type specificity involving generics and closures

[dktapps]

Bug report

The code can explain better than I can... In both cases the dumped type should be identical.

Code snippet that reproduces the problem

https://phpstan.org/r/31aaf10b-ceed-4ea2-a14c-6469190c2ee5

Expected output

The dumped type should be the same in both cases.

[ondrejmirtes]

Last night I came up with the idea that we mostly shouldn't generalize the generic type variables, except when they're in object generics, like Foo<int>.

Here's the resulting PR: phpstan/phpstan-src#2818

We can't do this for objects, because I want new Collection([1, 2, 3]) to become Collection<int>. This could be improved in the future thanks to this suggestion: #6732 (comment) (but it's pretty complex to implement so for now it has to wait).

The new behaviour now only applies to bleeding edge (https://phpstan.org/blog/what-is-bleeding-edge) so definitely enable it to get the taste of the future 👍

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.