Tyson Andre

Do this where practical. Only do this in limited subsets of ast nodes without side effects, e.g. where there are assignments by references (preg_match), regular assignments, etc. From the negation...

https://wiki.php.net/rfc/spread_operator_for_array - The linked PR was merged and has example code in the specification and with the phpt tests - [x] Support inferring the union type for arrays - [x]...

e.g. `@param 1|2|3|3 $value`

e.g. `$x == 'foo'` changed with the strict numeric comparisons RFC - it used to be true for the integer 0 Plugins may have similar checks

(if the real type could be inferred and is a literal string, false, true, etc., rather than a category such as `string`, `bool`, etc

If real types all match argument types in calls seen in that file, or (vacuously) there are no calls made in that file, and all real types in return statements...

These are commonly used, including in phan itself. For array_map. if the closure's type signature(s) can be determined (https://secure.php.net/array_map): - [x] Use the real/phpdoc return type of the closure passed...

Warn about mismatch of callables passed to usort, array_filter, array_map, etc

2

Related to #726 Also, warn about using uksort with a callable that doesn't accept int or strings, depending on the real array type.