Anders Jenbo

@staabm I'm pinging you here since the [original topic](https://github.com/phpstan/phpstan/issues/9498#issuecomment-1692788677) has been locked. If you are still willing to look in to the performance of Bladestan here is a small sample...

@staabm I already have a https://github.com/phpstan/phpstan#phpstan-pro subscription does that work?

That sounds like a really good idea, there are for sure something about the integration that are less then optimal.

This is most often cause by non-terminated lined PHP statements in the template. See https://github.com/TomasVotruba/bladestan/issues/57 for details. When you get a syntax error like this the line number is in...

> I assume that the standalone `@php()` directive is exempt? No, that is exactly where this issue normally arises. They are normally allowed in PHP but to analyze all of...

> resources/views/topic/content.blade.php > `@php use App\View\Support\EntityListLayout; @endphp` If this is a partial then you can't have use statements in it as it would result in things like: ```blade @foreach([1]) @include('topic.content')...

> I guess, also: do you know of any other problematic directives / bad practices to watch out for? I documented the issues i found here: https://github.com/TomasVotruba/bladestan/issues/created_by/AJenbo > Edit: for...

> Is there any way I could see more detailed output to trace the exact code output that causes the issue? I would suggest analyzing one file at a time,...

If that still doesn't give you a clear result then try removing 50% of the template until it parses succesfuld, the recover 25% and continue until you find the offending...

Closing as the original author has not provided the needed info