add another flag on SpecifiedTypes to not imply the opposite case

Bug report

... instead of generating weird faux functions calls, as we currently do (and a few 1st party extensions)

This is basically what https://phpstan.org/writing-php-code/narrowing-types#equality-assertions solves

So maybe instead of generating weird faux functions calls, we might add another flag on SpecifiedTypes to not imply the opposite case?
Also research how the equality assertion is currently implemented

(citing ondrej)

Code snippet that reproduces the problem

No response

Expected output

no more faux calls

Did PHPStan help you today? Did it make you happy in any way?

No response

This bug report is missing a link to reproduction at phpstan.org/try.

It will most likely be closed after manual review.

Add `setShouldNotImplyOppositeCase()` on `SpecifiedTypes` to replace …

Closed via merging phpstan/phpstan-src#5769

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.

Navigation Menu

Repository navigation

add another flag on SpecifiedTypes to not imply the opposite case #14705

Bug report

Code snippet that reproduces the problem

Expected output

Did PHPStan help you today? Did it make you happy in any way?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

add another flag on SpecifiedTypes to not imply the opposite case #14705

Description

Bug report

Code snippet that reproduces the problem

Expected output

Did PHPStan help you today? Did it make you happy in any way?

Activity

mergeable commented on May 26, 2026

phpstan-bot commented on Sep 20, 2026

github-actions commented on Oct 22, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions