Thinking about it once again, I really wonder if we need to deal with all "PHPStan specific" types in Symfony.

I understand that it can exist use cases, but I'm afraid to re-do a PHPStan in Symfony. Implementing all the types of https://phpstan.org/writing-php-code/phpdoc-types looks like a bad idea to me. IMHO, Symfony needs to understand structural information of types, but knowing that a string is escaped, or an integer is between a specific range is not needed often enough. WDYT?

(The same applies to #59676)

I tend to agree this goes beyond type-info’s scope.

I also agree.

Thus, the more complex our types become, the harder it becomes to define the API (see the phpstan type API).
If a project needs the full power of the phpstan type representation, they can depend on phpstan.

Fine. I'll close both PRs. I suppose this means #59827 will also not happen...

The array shape type is only one that is worth being merged in my opinion, as it is a structural and widely used type, such as list<foo> or iterable<bar>, which are already implemented.

Again thanks for having tried that, and for the great work here @DerManoMann 🙂

Just for the record - I've started moving my changes into a separate repo. Not ideal as it means forking at least the StringTypeResolver 🤷

https://github.com/DerManoMann/type-info-extras

Any issues around license, etc. let me know as they are not intentional.