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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

numeric-string not preserved when passed into generic constructor #5594

Closed
enumag opened this issue Sep 6, 2021 · 5 comments
Closed

numeric-string not preserved when passed into generic constructor #5594

enumag opened this issue Sep 6, 2021 · 5 comments
Labels
Milestone

Comments

@enumag
Copy link
Contributor

enumag commented Sep 6, 2021

Bug report

I hope I didn't make another mistake somewhere but this seems like a real bug to me. 馃

Code snippet that reproduces the problem

https://phpstan.org/r/6382fe16-7dad-44ae-ac6f-9fdac6f531cf

Expected output

no error

@ondrejmirtes ondrejmirtes added this to the Generics milestone Sep 6, 2021
@phpstan-bot
Copy link
Contributor

@enumag After the latest commit in dev-master, PHPStan now reports different result with your code snippet:

@@ @@
-9: Function createIterator() should return ArrayIterator<int|string, string&numeric> but returns ArrayIterator<(int|string), string>.
+7: Function createIterator() should return ArrayIterator<int|string, string> but return statement is missing.
Full report
Line Error
7 `Function createIterator() should return ArrayIterator<int

@phpstan-bot
Copy link
Contributor

@enumag After the latest commit in dev-master, PHPStan now reports different result with your code snippet:

@@ @@
-9: Function createIterator() should return ArrayIterator<int|string, string&numeric> but returns ArrayIterator<(int|string), string>.
+9: Function createIterator() should return ArrayIterator<int|string, numeric-string> but returns ArrayIterator<(int|string), string>.
Full report
Line Error
9 `Function createIterator() should return ArrayIterator<int

@Screenfeed
Copy link

Hi,
Sorry to zombify this ticket.

I have the same issue with array keys. See https://phpstan.org/r/fa4bb809-0552-4dcf-ae81-267c1bb35386.

@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.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants