You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When bleeding edge is enabled, since 1.10.48 we've noticed that generic types that were previously correctly remembered now appear "one level simplified" and thus imprecise, leading to mismatches with expectations of rest of the codebase.
In the playground, even with bleeding edge on, lines 93, 96 & 97 all should report int<0, max> instead of just int (more precise type is still remembered on line 88).
Did PHPStan help you today? Did it make you happy in any way?
It makes our whole team at ContentKing happy every day, helps the speed of development tremendously!
The text was updated successfully, but these errors were encountered:
Bug report
When bleeding edge is enabled, since 1.10.48 we've noticed that generic types that were previously correctly remembered now appear "one level simplified" and thus imprecise, leading to mismatches with expectations of rest of the codebase.
Code snippet that reproduces the problem
https://phpstan.org/r/08da8393-113a-4377-930e-f4bd6b442445
Expected output
In the playground, even with bleeding edge on, lines 93, 96 & 97 all should report
int<0, max>
instead of justint
(more precise type is still remembered on line 88).Did PHPStan help you today? Did it make you happy in any way?
It makes our whole team at ContentKing happy every day, helps the speed of development tremendously!
The text was updated successfully, but these errors were encountered: