I'm not sure enough for what this test is intended to do, so cannot change it yet. c36df00

I think I understood it.

@ondrejmirtes
Sorry for lack of explanation.
The purpose of this pull request is to make isUndefinedExpressionAllowed === true && $isOffsetAccessible->maybe() and isSpecified === true && $isOffsetAccessible->maybe() which is a kind of breaking change in some cases so we need some fix in tests too (see aeb00d9).

This change can make
https://phpstan.org/r/ea075526-a29b-428a-a5f7-39b90266a2f8

this code not report, and I believe this shouldn't be reported because this is a valid PHP code.

#1312 (comment)

unset is also a method that causes isUndefinedExpressionAllowed === true so the result for this test changes.
c36df00
Looking at this commit I thought that unset was not important here, because the intention of this test was to test reportMaybes for level 7 and unset isn't related. This is why I had to change the existing test.

Although, I remembered now this issue phpstan/phpstan#7073 and noticed that I have to be careful for array access on object type (because it is a fatal error) and this PR needs some modification anyway.

All of that is totally fine, I just want both unset and var_dump tested in that file. It's OK if the error for unset() changes/disappears.

I see, thanks.
I’ll mark this ready after fixing that and fixing problems about object type.
Thank you very much for reviewing!

https://3v4l.org/HrulF
Memo for canAccessProperties and isOffsetAccessible.

@ondrejmirtes
I'll mark this ready.

I will implement a more strict behavior for canAccessProperties and isOffsetAccessible maybes under isUndefinedExpressionAllowed === true in another pull request using the result of https://3v4l.org/HrulF

memo
php/php-src@008bfcc

Thank you!