Integer ranges in array keys do not carry through generics

[lcdennison]

Bug report

Using 1.5.7.

In the below example link, I created two methods (foo and bar) that accept an array parameter. foo declares an explicit return of array<int<0,max>, mixed>, whereas bar uses generics to simply pass through the input type. The class has two properties, array1 and array2 that both expect array<int<0,max>, mixed>. The result of foo can be successfully assigned to a property, but the result of bar cannot. It would seem the generics I used for bar do not carry through the integer range int<0,max> for keys. It comes out as simply int.

Or I'm using generics incorrectly?

Code snippet that reproduces the problem

https://phpstan.org/r/e9901d5a-abb7-47ba-8706-204c3890a6fb

Expected output

I'd expect integer ranges to be carried through the generics.

[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.