i'm just proof of concepting some ideas i've had for rules that catch common performance drains i've seen in laravel codebases, there's a lot of thinking to be done yet but i'm just seeing if i can identify the obvious cases first and then make them more robust after trying it on some real world projects

for example, calling config() helper with a constant string inside iteration, as the helper reaches out to the dependency container, which is a lot of work that could be avoided by doing it before:

foreach ($values as $value) {
    $someConfigValue = config('config-key');
    
    $this->doSomething($someConfigValue);
}

should be

$someConfigValue = config('config-key');

foreach ($values as $value) {
        $this->doSomething($someConfigValue);
}

tried the rich parser visitor and it works a charm, thank you!

Just be careful and make sure it also works for nested loops 😊

pre-empted a bug, i was naively using bool when i needed int, nice one!