Internal error: Failed to find parent class of constant

[vworldat]

Bug report

Phpstan fails to find class constants when used as default argument value in a trait method. I have backtracked various phpstan versions. This has not been an issue up until phpstan 0.12.25, from 0.12.26 onwards it breaks on all versions i checked including the latest 0.12.58.

Code snippet that reproduces the problem

https://phpstan.org/r/c17faf82-5d21-4283-a324-b5976c6c1414

Things I have tried to make it pass:

• constant visibility does not matter
• method visibility does not matter
• declaring class as final or not does not matter
• the class extending a parent class does not matter
• not declaring strict types does not matter
• accessing the same constant from inside the method's body instead of the argument default value works fine: https://phpstan.org/r/2dd6fcf6-b07d-4ea6-9958-97c7393d24f0

Expected output

No errors.

[phpstan-bot]

@vworldat PHPStan now reports different result with your code snippet:

@@ @@
 -1: Internal error: Failed to find parent class of constant "DEFAULT_SIZE".
 Run PHPStan with --debug option and post the stack trace to:
-https://github.com/phpstan/phpstan/issues/new
+https://github.com/phpstan/phpstan/issues/new?template=Bug_report.md

Full report

Line	Error
-1	Internal error: Failed to find parent class of constant "DEFAULT_SIZE". Run PHPStan with --debug option and post the stack trace to: https://github.com/phpstan/phpstan/issues/new?template=Bug_report.md

[ondrejmirtes]

Realized this is duplicate of #4066

[ondrejmirtes]

Actually isn't :)

[ondrejmirtes]

Fixed by: ondrejmirtes/BetterReflection@4fafef2 + phpstan/phpstan-src@8babba3

[phpstan-bot]

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

@@ @@
--1: Internal error: Failed to find parent class of constant "DEFAULT_SIZE".
-Run PHPStan with --debug option and post the stack trace to:
-https://github.com/phpstan/phpstan/issues/new
+No errors

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