← All results

@phan-debug-var

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

Phan requires a *string expression statement* (not a comment) so the AST exposes the annotation. Honouring it means a PhanDebugAnnotation with the inferred union type. Other tools usually see a no-op string statement and may report "expression has no effect" / "does not do anything" — that is style noise, not feature enforcement, so it is marked // E?[noise]. Phan attributes the diagnostic to the enclosing statement line (if), not to the string line itself. The enforcement probe therefore sits on the if. References: - Phan Annotating-Your-Source-Code-V6.md: @phan-debug-var

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 Enforced
debug_phan_debug_var.php:27: @phan-debug-var requested for variable $value - it has union type int(real=int) [PhanDebugAnnotation]
  • Recognition: spelling resolved
  • Enforcement: 1/1 of the expected violations reported
phpstan 2.3.1PHPStan - PHP Static Analysis Tool 2.3.1 Not enforced reported Lv.4+
debug_phan_debug_var.php:29: Expression "'@phan-debug-var $value'" on a separate line does not do anything. [reported-from-level=4]
With strict-rules
debug_phan_debug_var.php:29: Expression "'@phan-debug-var $value'" on a separate line does not do anything.
  • Recognition: spelling resolved
  • Enforcement: 0/1 of the expected violations reported
psalm 6.20.0Psalm 6.20.0@804f03c0c183d149fcd4b8c7c0c9b3fbf836d34c
next: 7.0.0-rc2
Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/1 of the expected violations reported
mago 1.57.0mago 1.57.0 Not enforced
debug_phan_debug_var.php:29: Expression has no effect as a statement [unused-statement]
  • Recognition: spelling resolved
  • Enforcement: 0/1 of the expected violations reported
mir 0.87.0mir 0.87.0 Not enforced

No diagnostics reported.

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

No diagnostics reported.

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

No diagnostics reported.

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

No diagnostics reported.

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

No diagnostics reported.

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

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/1 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
debug_phan_debug_var.php:29: Expression evaluated but not used [discardExpr]
  • Recognition: spelling resolved
  • Enforcement: 0/1 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/1 of the expected violations reported
phpstan-strict 2.3.1PHPStan - PHP Static Analysis Tool 2.3.1 Not enforced
debug_phan_debug_var.php:29: Expression "'@phan-debug-var $value'" on a separate line does not do anything.
  • Recognition: spelling resolved
  • Enforcement: 0/1 of the expected violations reported
psalm-next 7.0.0-rc2Psalm 7.0.0-rc2@20339e3fe5b8d03bcd8061030eb2a83ad50e5783 Not enforced

No diagnostics reported.

  • Recognition: spelling resolved
  • Enforcement: 0/1 of the expected violations reported

Source

<?php

declare(strict_types=1);

namespace Conformance\Tests\DebugPhanDebugVar;

/**
 * Cross-tool handling of `@phan-debug-var`.
 *
 * Phan requires a *string expression statement* (not a comment) so the AST
 * exposes the annotation. Honouring it means a `PhanDebugAnnotation` with the
 * inferred union type. Other tools usually see a no-op string statement and
 * may report "expression has no effect" / "does not do anything" — that is
 * style noise, not feature enforcement, so it is marked `// E?[noise]`.
 *
 * Phan attributes the diagnostic to the enclosing statement line (`if`), not
 * to the string line itself. The enforcement probe therefore sits on the `if`.
 *
 * References:
 * - Phan Annotating-Your-Source-Code-V6.md: `@phan-debug-var`
 *
 * @conformance-kind debug
 */

function example(int|string $value): void // T: @phan-debug-var
{
    if (\is_int($value)) { // E?: PhanDebugAnnotation is attributed here (enclosing statement)
        // Must be a bare string statement — php-ast does not surface comments.
        '@phan-debug-var $value'; // E?[noise]: non-Phan "no effect" / unused-statement noise — not enforcement
    }
}