This doesn't have tests. I didn't add a config yet.
This is hardcoded as true for now.
Workarounds for high error rates planned:
Make ConditionVisitor guess an array shape in preg_match
Reduce false positives for self-analysis, e.g. str_replace
(array->array, string->string, and only those)
File-level suppressions for strict issues?
Array access looks like it always includes |null right now for the inferred type (Except for array shapes?)
Create narrower issue types for PossiblyFalse, PossiblyNull, and PossiblyInvalid when at least one type is accepted. If the only rejected type is false, emit PossiblyFalse, etc.
This doesn't have tests. I didn't add a config yet.
This is hardcoded as true for now.
Workarounds for high error rates planned:
|null
right now for the inferred type (Except for array shapes?)For https://github.com/phan/phan/issues/879