False positive `Strict comparison using ===` when `treatPhpDocTypesAsCertain` is `false`

[canvural]

Bug report

Code snippet that reproduces the problem

<?php

function foo(int ...$foo): void {
    var_dump($foo === []);
}

foo();
foo(5);

When treatPhpDocTypesAsCertain is true there is no error reported for the above code: https://phpstan.org/r/df01e23e-636a-4d09-b106-806a14fd46ed

But when treatPhpDocTypesAsCertain is false, there is Strict comparison using === between array<int, int> and array() will always evaluate to false.: https://phpstan.org/r/16b5347b-fd04-4ae9-be7a-366f87918cac

Calling foo with no arguments is valid: https://3v4l.org/lmbDD

Expected output

No error in both cases.

[phpstan-bot]

@canvural After the latest commit in dev-master, PHPStan now reports different result with your code snippet:

@@ @@
-4: Strict comparison using === between array<int, int> and array() will always evaluate to false.
+4: Strict comparison using === between array<int, int> and array{} will always evaluate to false.

Full report

Line	Error
4	Strict comparison using === between array<int, int> and array{} will always evaluate to false.

[phpstan-bot]

@canvural After the latest commit in dev-master, PHPStan now reports different result with your code snippet:

@@ @@
-4: Strict comparison using === between array<int, int> and array() will always evaluate to false.
+PHP 8.0 (1 error)
+==========
+
+4: Strict comparison using === between array<int|string, int> and array{} will always evaluate to false.
+
+PHP 7.1 – 7.4 (1 error)
+==========
+
+4: Strict comparison using === between array<int, int> and array{} will always evaluate to false.

Full report

PHP 8.0 (1 error)

Line	Error
4	`Strict comparison using === between array<int

PHP 7.1 – 7.4 (1 error)

Line	Error
4	Strict comparison using === between array<int, int> and array{} will always evaluate to false.

[ondrejmirtes]

Fixed: phpstan/phpstan-src@a5447db

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.