@psalm-assert iterable<T1|T2> isn't being picked up, and leads to failed type inference

[Ocramius]

https://psalm.dev/r/e07c4aaa1c

<?php

/** @psalm-assert iterable<positive-int|0> $input */
function assertAllNatural(mixed $input): void {throw new \Exception(\var_export($input, true));}

function allNatural(mixed $input): array
{
    assertAllNatural($input);
    return $input;
}

In this case, the entire type assertion @psalm-assert iterable<positive-int|0> is being suppressed, and psalm cannot infer the type of $input

Ref: https://symfony-devs.slack.com/archives/C8SFXTD2M/p1611068007070700

Quoting:

ocramius  3:53 PM
BTW, is @psalm-assert iterable<positive-int|0> intentionally not working / limitation, or a bug, in your opinion?
muglug  3:56 PM
certainly not intentional
ocramius  4:12 PM
will report, but mostly for reference first :slightly_smiling_face:

[psalm-github-bot]

I found these snippets:

https://psalm.dev/r/e07c4aaa1c

<?php

/** @psalm-assert iterable<positive-int|0> $input */
function assertAllNatural(mixed $input): void {throw new \Exception(\var_export($input, true));}

function allNatural(mixed $input): array
{
    assertAllNatural($input);
    return $input;
}

Psalm output (using commit 2f58c6a):

INFO: MixedReturnStatement - 9:12 - Could not infer a return type

INFO: MixedInferredReturnType - 6:36 - Could not verify return type 'array<array-key, mixed>' for allNatural

[weirdan]

This seems to have been fixed already: https://psalm.dev/r/f514529cce

[psalm-github-bot]

I found these snippets:

https://psalm.dev/r/f514529cce

<?php

/** @psalm-assert iterable<positive-int|0> $input */
function assertAllNatural(mixed $input): void {throw new \Exception(\var_export($input, true));}

function allNatural(mixed $input): iterable
{
    assertAllNatural($input);
    /** @psalm-trace $input */;
    return $input;
}

Psalm output (using commit 3c66b75):

INFO: Trace - 9:31 - $input: iterable<mixed, 0|positive-int>