positive-intpositive-int is a refinement of int, so a @return positive-int value
always satisfies a native int parameter — analyzers that do not model the
range still fall back to int. Range-aware analyzers additionally reject a
value known to be out of range; others accept it under the int fallback.
References:
- PHPStan TypeNodeResolver positive-int resolves to IntegerRangeType(1, null)| Analyzer | Version | Result | Diagnostics |
|---|---|---|---|
| phan | 6.0.10Phan 6.0.10 php-ast version 1.1.3 PHP version used to run Phan: 8.5.11 | Enforced | phpdoc_advanced_fallback_positive_int.php:46: Argument 1 ($value) is -1 of type int (value: -1) but \Conformance\Tests\PhpdocAdvancedFallbackPositiveInt\acceptsPositiveInt() takes positive-int defined at /Users/megurine/repo/php/php-typing-conformance/conformance/tests/phpdoc_advanced_fallback_positive_int.php:34 [PhanTypeMismatchArgument]
|
| phpstan | 2.3.1PHPStan - PHP Static Analysis Tool 2.3.1 | Enforced reported Lv.5+ | phpdoc_advanced_fallback_positive_int.php:46: Parameter #1 $value of function Conformance\Tests\PhpdocAdvancedFallbackPositiveInt\acceptsPositiveInt expects int<1, max>, -1 given. [reported-from-level=5] With strict-rulesphpdoc_advanced_fallback_positive_int.php:46: Parameter #1 $value of function Conformance\Tests\PhpdocAdvancedFallbackPositiveInt\acceptsPositiveInt expects int<1, max>, -1 given.
|
| psalm | 6.20.0Psalm 6.20.0@804f03c0c183d149fcd4b8c7c0c9b3fbf836d34c next: 7.0.0-rc2 |
Enforced | phpdoc_advanced_fallback_positive_int.php:46: Argument 1 of Conformance\Tests\PhpdocAdvancedFallbackPositiveInt\acceptsPositiveInt expects int<1, max>, but -1 provided [InvalidArgument]
|
| mago | 1.57.0mago 1.57.0 | Enforced | phpdoc_advanced_fallback_positive_int.php:46: Invalid argument type for argument #1 of `Conformance\Tests\PhpdocAdvancedFallbackPositiveInt\acceptsPositiveInt`: expected `positive-int`, but found `int(-1)`. [invalid-argument]
|
| mir | 0.87.0mir 0.87.0 | Enforced | phpdoc_advanced_fallback_positive_int.php:46: InvalidArgument: Argument $value of acceptsPositiveInt() expects 'positive-int', got '-1' [MIR0201]
|
| phpantom | 0.11.1phpantom_lsp 0.11.1 | Enforced | phpdoc_advanced_fallback_positive_int.php:46: Argument 1 ($value) expects positive-int, got -1 [type_mismatch_argument]
|
| intelephense | 1.18.5intelephense 1.18.5 | Widened to int | No diagnostics reported.
|
| phpactor | 2026.10.07.0Phpactor 2026.10.07.0 | Not enforced | No diagnostics reported.
|
| phpy | 1.0.19409phpy 1.0.19409 | Not enforced | No diagnostics reported.
|
| qodana | 262.10968.76PhpStorm 262.10968.76 | Widened to int | No diagnostics reported.
Notes: Checked as plain `int`: a wrong type is reported as "Expected parameter of type 'int'", and `-1` passes, exactly as for `@param int`. Quick Documentation still shows `positive-int`, so the spelling is recognised and only the refinement is dropped. |
| noverify | 0.5.5NoVerify, version 0.5.5: built on: 2025.04.22 14:36:46 OS: r-kuchinskas arm64 Commit: 4774b82f8adc53fbef38f95e97af4b953b4d1529 | Widened to int | No diagnostics reported.
Notes: NoVerify does not model the integer range and falls back to `int`, so it accepts the out-of-range `-1`. The other analyzers enforce `positive-int` and reject it. |
| steins | 0.1.8steins 0.1.8 (2026-09-21 revision 76306a9) | Enforced | phpdoc_advanced_fallback_positive_int.php:46: argument -1 to acceptsPositiveInt() violates declared @param positive-int $value — declared contract violation [phpdoc.param-mismatch]
|
| phpstan-strict | 2.3.1PHPStan - PHP Static Analysis Tool 2.3.1 | Enforced | phpdoc_advanced_fallback_positive_int.php:46: Parameter #1 $value of function Conformance\Tests\PhpdocAdvancedFallbackPositiveInt\acceptsPositiveInt expects int<1, max>, -1 given.
|
| psalm-next | 7.0.0-rc2Psalm 7.0.0-rc2@20339e3fe5b8d03bcd8061030eb2a83ad50e5783 | Enforced | phpdoc_advanced_fallback_positive_int.php:46: Argument 1 of Conformance\Tests\PhpdocAdvancedFallbackPositiveInt\acceptsPositiveInt expects int<1, max>, but -1 provided [InvalidArgument]
|
<?php
declare(strict_types=1);
namespace Conformance\Tests\PhpdocAdvancedFallbackPositiveInt;
/**
* `positive-int`
*
* `positive-int` is a refinement of `int`, so a `@return positive-int` value
* always satisfies a native `int` parameter — analyzers that do not model the
* range still fall back to `int`. Range-aware analyzers additionally reject a
* value known to be out of range; others accept it under the `int` fallback.
*
* References:
* - PHPStan TypeNodeResolver `positive-int` resolves to IntegerRangeType(1, null)
*/
/**
* @return positive-int
*/
function returnsPositiveInt() // T: positive-int
{
return 5; // V
}
function acceptsInt(int $value): void
{
}
/**
* @param positive-int $value
*/
function acceptsPositiveInt($value): void // T: positive-int
{
}
// A `positive-int` value always satisfies a native `int` parameter.
acceptsInt(returnsPositiveInt()); // V
// A literal positive integer satisfies the refined parameter.
acceptsPositiveInt(5); // V
// A negative literal is out of range; range-aware analyzers reject it, others
// fall back to `int` and accept it.
acceptsPositiveInt(-1); // E?: negative int should be rejected where positive-int is required