Skip to content
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

Template type lost #7944

Closed
dragosprotung opened this issue Sep 6, 2022 · 3 comments
Closed

Template type lost #7944

dragosprotung opened this issue Sep 6, 2022 · 3 comments

Comments

@dragosprotung
Copy link

Bug report

Code snippet that reproduces the problem

https://phpstan.org/r/a37ea7d6-2c1d-44d1-8257-338d6ffe8465

Expected output

The two types should be the same

@ondrejmirtes ondrejmirtes added this to the Generics milestone Sep 6, 2022
@rvanvelzen
Copy link
Contributor

This is due to generalizing of template types. See phpstan/phpstan-src#1206

@ondrejmirtes
Copy link
Member

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 👍

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants