Nicolas Grekas

Nope sorry I need help also.

@julienfalque thanks for the hint. I tried it on the symfony code base, and it also changes function calls, no only signatures. Only signatures should be forced on a single...

Something like that yes, but specific to null defaults. Because otherwise `nullable_type_declaration_for_default_null_value` is not safe since it will generate code that will trigger new deprecations, see https://3v4l.org/nSpos

I also posted https://github.com/php/php-src/issues/13353

From the end user pov, the current behavior is risky because it turns a non-deprecated syntax: `(int $a = null, $b)` into a deprecated one: `(?int $a = null, $b)`.

Yes, this changes makes sense (but I didn't think about the PHP-version issue - maybe "parameters" should be turned on only on PHP 8 that's what you mean?)

Can you please try again after upgrading composer to the latest version?

Can you please give me the full list of reproducing steps?

Hi, I'm not sure I understand the motivation for this change. What's the relation to the `file` processor?

:+1: for parallel