support // lint comments

[staabm]

running name-collision detector on a repository containing a file with PHP 8.5+ only syntax like e.g.

<?php // lint >= 8.5

namespace Bug14565;

class Foo
{

	#[\NoDiscard]
	public function bar(): int
	{
		return 1;
	}

}

function (Foo $foo): void {
	(void) $foo->bar();
};

turns into a fatal error

php vendor/bin/detect-collisions --configuration collision-detector.json
Using config '/Users/staabm/workspace/phpstan-strict-rules/collision-detector.json'

ERROR: Unable to parse /Users/staabm/workspace/phpstan-strict-rules/tests/Rules/Cast/data/bug-14565.php: syntax error, unexpected variable "$foo"

make: *** [name-collision] Error 255

when running on a lower PHP version

php -v     
PHP 8.3.30 (cli) (built: Jan 13 2026 22:36:55) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.30, Copyright (c) Zend Technologies

in php-parallel-lint there is a <?php // lint >= 8.5 syntax.
I think it would be great if collision-detector could also utilize this syntax and auto-skip files which do not match against the current used php version.
that way we would not need to maintain another "exlucde" list in collision-detector.json.

[janedbal]

What is the actual usecase? I'd expect this tool to use the PHP version the codebase uses, not lower.

Also, you can skip parse failures:

{
    "ignoreParseFailures": true // skip files with parse errors
}

[staabm]

my use-case is, that I run sometimes collision detector locally with my workstations PHP version and this version is in the supported range of e.g. phpstan-strict-rules projects composer constraint. but I get errors when I don't use PHP 8.5+ because some files require PHP8.5 syntax (and these files already contain such // lint comments because of other tools needs).

In CI the tool always runs on a very recent php version so its not a problem there.

the files in question are test-fixtures, so some of them have a higher min-version than the project itself has.
example file