← All results

@psalm-check-type / @psalm-check-type-exact

Group: Debug features · Category: extension · File: debug_psalm_check_type.php

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

Analyzer results

AnalyzerVersionResultDiagnostics
phan 6.0.10Phan 6.0.10 php-ast version 1.1.3 PHP version used to run Phan: 8.5.11 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
phpstan 2.3.1PHPStan - PHP Static Analysis Tool 2.3.1 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
psalm 6.20.0Psalm 6.20.0@804f03c0c183d149fcd4b8c7c0c9b3fbf836d34c
next: 7.0.0-rc2
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]
  • Recognition: spelling resolved
  • Enforcement: 2/2 of the expected violations reported
mago 1.57.0mago 1.57.0 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
mir 0.87.0mir 0.87.0 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
phpantom 0.11.1phpantom_lsp 0.11.1 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
intelephense 1.18.5intelephense 1.18.5 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
phpactor 2026.10.07.0Phpactor 2026.10.07.0 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
phpy 1.0.19409phpy 1.0.19409 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
qodana 262.10968.76PhpStorm 262.10968.76 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations 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.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
steins 0.1.8steins 0.1.8 (2026-09-21 revision 76306a9) Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
phpstan-strict 2.3.1PHPStan - PHP Static Analysis Tool 2.3.1 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/2 of the expected violations reported
psalm-next 7.0.0-rc2Psalm 7.0.0-rc2@20339e3fe5b8d03bcd8061030eb2a83ad50e5783 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]
  • Recognition: spelling resolved
  • Enforcement: 2/2 of the expected violations reported

Source

<?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
}