kkmuffme

If you enable https://psalm.dev/docs/running_psalm/configuration/#ensurearraystringoffsetsexist in your config, do you still get this error?

It's a bug bc of the `true` values - works fine with `isset` https://psalm.dev/r/6de6380bf7 Possibly the issue happens from https://github.com/vimeo/psalm/blob/5.x/src/Psalm/Internal/Analyzer/Statements/Expression/EmptyAnalyzer.php#L62 and below I would check if it's reporting as possibly...

The callback for `array_walk` doesn't have more specific types in psalm's callmap. Ideally the annotation would be `callable(&value-of, key-of, mixed=)` or even better to create a separate \2 annotation where...

Yes, I do use the latest parser already: >composer show | grep parser nikic/php-parser v4.16.0 A PHP parser written in PHP phpstan/phpdoc-parser 1.23.1 PHPDoc parser with support for nullable, intersection...

Thanks! Could this issue get fixed in the way PHPCSExtra does? I inherit this rule from WPCS, should I bring the issue up there too? (asking since you're contributing there...

Another one that is purely stylistic is `capitalized-comments` which should be moved to @stylistic

The strlen thing is a duplicate of https://github.com/vimeo/psalm/issues/7387 >strange behavior with the empty function. Please elaborate, I don't see any strange behavior there.

@koto @mgol Chrome 107 setHTML is only about 4 times slower than no sanitizing, however at 45k/ops/sec (compared to 185k/ops/sec without setHTML) it's so fast, there won't be any feelable...

+1, that would be really great if that were possible

Changed various things to handle more common cases and excluded things that won't work. Overall works quite well, feedback appreciated so this can get merged eventually