Description
While looking at php-typing-conformance, I came across PHP;STEINS:
https://github.com/rigortype/steins
PHPantom and PHP;STEINS have different primary goals, but there seems to be some meaningful overlap:
- both are written in Rust
- both build on Mago-related parsing infrastructure
- both implement advanced PHP/PHPDoc type inference
- both care about low-noise diagnostics
- PHP;STEINS has an LSP preview on its roadmap, while PHPantom already has a mature LSP implementation
I am not suggesting merging the projects or changing either roadmap.
It might simply be useful for the maintainers to be aware of each other and consider whether some areas could be shared or coordinated, for example:
type-system and conformance test fixtures
- PHP/PHPDoc semantics
- Mago-related parser work
- possibly supporting PHP;STEINS as an external analyzer backend in PHPantom in the future
Use case
Avoid duplicating difficult PHP type-system and static-analysis work where both projects are solving similar problems.
PHPantom could stay focused on editor intelligence, navigation, framework awareness, and LSP functionality, while PHP;STEINS could continue focusing on deeper static analysis.
Even limited cooperation, such as sharing conformance fixtures or discussing type-system edge cases, could benefit both projects without coupling their architectures.
Proposed solution
No response
Alternatives considered
No response
Code example
Description
While looking at php-typing-conformance, I came across PHP;STEINS:
https://github.com/rigortype/steins
PHPantom and PHP;STEINS have different primary goals, but there seems to be some meaningful overlap:
I am not suggesting merging the projects or changing either roadmap.
It might simply be useful for the maintainers to be aware of each other and consider whether some areas could be shared or coordinated, for example:
type-system and conformance test fixtures
Use case
Avoid duplicating difficult PHP type-system and static-analysis work where both projects are solving similar problems.
PHPantom could stay focused on editor intelligence, navigation, framework awareness, and LSP functionality, while PHP;STEINS could continue focusing on deeper static analysis.
Even limited cooperation, such as sharing conformance fixtures or discussing type-system edge cases, could benefit both projects without coupling their architectures.
Proposed solution
No response
Alternatives considered
No response
Code example