@psalm-check-type / @psalm-check-type-exactCheckType issue
only where the inferred type does not match. The two spellings differ in
how strict the match is — @psalm-check-type accepts a subtype (the
literal 2 matches int), @psalm-check-type-exact demands the exact
type. A matching assertion is silent, so only the mismatch lines are
enforcement probes; the matching lines carry E?[noise] to tolerate a
tool that parses the tag and stumbles.
Attribution: Psalm blames the statement that follows the annotation, not
the docblock line, so the probes sit on those statements; the docblock
lines are kept free of trailing // comments for hygiene.
References:
- Psalm running_psalm/issues/CheckType.md| Analyzer | Version | Result | Diagnostics |
|---|---|---|---|
| phan | 6.0.7Phan 6.0.7 php-ast version 1.1.3 PHP version used to run Phan: 8.5.9 | Not enforced | No diagnostics reported.
|
| phpstan | 2.2.8PHPStan - PHP Static Analysis Tool 2.2.8 | Not enforced | No diagnostics reported.
|
| psalm | 6.16.1Psalm 6.16.1@f1f5de594dc76faf8784e02d3dc4716c91c6f6ac next: 7.0.0-beta19 |
Enforced | debug_psalm_check_type.php:37: Checked variable $x = 1 does not match $x = 2 [CheckType] debug_psalm_check_type.php:48: Checked variable $x = int does not match $x = 2 [CheckType]
|
| mago | 1.46.0mago 1.46.0 | Not enforced | No diagnostics reported.
|
| mir | 0.70.1mir 0.70.1 | Not enforced | No diagnostics reported.
|
| phpantom | 0.9.0phpantom_lsp 0.9.0 | Not enforced | No diagnostics reported.
|
| intelephense | 1.18.5intelephense 1.18.5 | Not enforced | No diagnostics reported.
|
| phpy | 0.2.0phpy 0.2.0 | Not enforced | No diagnostics reported.
|
| qodana | 262.8665.325Qodana 262.8665.325 | Not enforced | No diagnostics reported.
|
| noverify | 0.5.5NoVerify, version 0.5.5: built on: 2025.04.22 14:36:46 OS: r-kuchinskas arm64 Commit: 4774b82f8adc53fbef38f95e97af4b953b4d1529 | Not enforced | No diagnostics reported.
|
| steins | 0.1.5steins 0.1.5 (2026-08-12 revision 39b4cc1) | Not enforced | No diagnostics reported.
|
| phpstan-strict | 2.2.8PHPStan - PHP Static Analysis Tool 2.2.8 | Not enforced | No diagnostics reported.
|
| psalm-next | 7.0.0-beta19Psalm 7.0.0-beta19@7e751c06a756fa64dc4c759c09fe4a173afcb433 | Enforced | debug_psalm_check_type.php:37: Checked variable $x = 1 does not match $x = 2 [CheckType] debug_psalm_check_type.php:48: Checked variable $x = int does not match $x = 2 [CheckType]
|
<?php
declare(strict_types=1);
namespace Conformance\Tests\DebugPsalmCheckType;
/**
* Cross-tool handling of `@psalm-check-type` / `@psalm-check-type-exact`.
*
* Psalm's assert-style inspection tags: the docblock states the type a
* variable should have at that point, and Psalm reports a `CheckType` issue
* only where the inferred type does not match. The two spellings differ in
* how strict the match is — `@psalm-check-type` accepts a subtype (the
* literal `2` matches `int`), `@psalm-check-type-exact` demands the exact
* type. A matching assertion is silent, so only the mismatch lines are
* enforcement probes; the matching lines carry `E?[noise]` to tolerate a
* tool that parses the tag and stumbles.
*
* Attribution: Psalm blames the statement that follows the annotation, not
* the docblock line, so the probes sit on those statements; the docblock
* lines are kept free of trailing `//` comments for hygiene.
*
* References:
* - Psalm running_psalm/issues/CheckType.md
*
* @conformance-kind debug
*/
function checkTypeExample(): void // T: @psalm-check-type
{
$x = 2;
/** @psalm-check-type $x = int */
echo $x; // E?[noise]: matching assertion — the literal 2 is an int, silence expected
/** @psalm-check-type $x = 1 */
echo $x; // E?: 2 is not the literal 1 — the sole enforcement probe
}
function checkTypeExactExample(): void // T: @psalm-check-type-exact
{
$x = 2;
/** @psalm-check-type-exact $x = 2 */
echo $x; // E?[noise]: exact match, silence expected
/** @psalm-check-type-exact $x = int */
echo $x; // E?: 2 is not exactly int — the sole enforcement probe
}