This is incredibly interesting. Thanks for mentioning it. Unfortunately it’s not yet ready:

https://phprust.com/status/

I’ll keep checking

It runs everything that any software I've ever written needs - and I've been doing PHP since dates began with `19`.

But since php isn’t complied, how would I know if something is broken until every code path is exercised? Genuine question

You exercise every code path with a unit or integration test.

I tend to write integration tests for the paths users take through the application (website), and fill in the holes with unit tests. I'll also write unit tests for methods that change often or are critical, such as business logic.

I wonder if PHP compiled with Fil-C would have stopped that bug. My guess is it would have.

My tests show that it would. The post-patch integration tests trap under Fil-C, and the StealMyBitcoin exploit chain traps too.

https://mbrock.github.io/filnix/docs/php.html

It’s also compatible with most PHP native extensions.