markus staab | @[email protected]

Do you need help with #PHPStan in some form? I have plenty of experience in contributing changes to PHPStan core, or implementing custom extensions. staabm.github.io/2024/01/01/php… plz RT

I had a bad hair day at PHP UK but I think this talk recording is still worth your time.

Why Array String Keys Are Not Type-Safe in PHP And What Will PHPStan Do About It: phpstan.org/blog/why-array…

dumdidum.. 🚀 #phpstan

Recently I learned that the order in which you pass options to a CLI command can have a huge perf impact on the runtime (even if it leads the same result)

It was a pleasure to work with @MisterDeviling thru a lot of old #PHPStan bugs. Yesterdays release contains a massive package of fixes. while we concentrated on the maintenance parts, ondrej could concentrate his efforts on improving DX with better docs and other nice additions.

New release: PHPStan 2.1.41 github.com/phpstan/phpsta… #phpstan

my non-scientific benchmark suggests running #PHPStan on #wordpress core, will be a lot faster starting with the next release

Lightweight fork of Xdebug 🧪 You can keep it always enabled as it has only ~5% overhead compared to ~300% in Xdebug

Error identifiers documentation is finally useful! Take a while and browse everything PHPStan can report:

For the longest time I was bothered that “Documentation” link on phpstan.org led directly to “Getting Started” page, and that some really useful docs pages weren’t discoverable at all. Starting today, it’s boxes describing what use-case/problem the page solves.

Achievement unlocked: crossed the 1000 commits line in @phpstan core

In case your daily #phpstan run takes minutes instead of seconds you likely don’t utilize the result cache. Find solutions at staabm.github.io/2023/10/21/php…

Several times a week I tell people their problem can be solved by adding @​phpstan-impure above their non-void function (or by setting rememberPossiblyImpureFunctionValues: false). Finally, PHPStan will tell them by itself:

💥Big release of Dead Code Detector via @phpstan: 🏷️Dead properties: Both never-written & never-read detected! Property hooks part of transitivity chain! ☘️Twig support! Parameters passed to templates are used! github.com/shipmonk-rnd/d…

@alexdaubois Main problem is performance for me. I have a dedicated CLI command to enable/disable loading of the xdebug extension to work arround it - and I need it tens of times daily

How can we improve the debugger situation in #PHP? Compared to other languages, the majority of people use dd() and dump() (myself included!). How could we change that? What the biggest friction point?

We made AND and OR-conditions faster to analyse in #phpstan. In some codebases this has some serious perf implications :-)

How fast can you make it? Here's the 100-million-row challenge in #PHP: stitcher.io/feed/posts/743… You have two weeks to participate. Thanks to @phpstorm and @tideways for sponsoring the prizes!

@freekmurze you might be interessted in github.com/olvlvl/compose… dumps the relevant information at "composer install"-time and therefore is super fast

🚀 We just released spatie/php-attribute-reader, a package that gives you a clean API for reading PHP attributes. PHPs reflection API for attributes is surprisingly verbose. Our package fixes that. 👍 #php

@HugoAlliaume I guess I hit a may commandlen, because my command get cut in middle of a option value

@markusstaab It’s not something about the number or arguments?

TIL: your github action might fail because of a overlong command line, which gets cut without further notice. Not sure its a #php or #windows or #githubactions effect. 1:1 the same command works on a ubuntu based github action without error