Is this intentional?

/** @param array{foo?: int} $a */
function test(array $a): void {
	\PHPStan\dumpType($a['foo']); // int
}

/** @param object{foo?: int} $o */
function test(object $o): void {
    \PHPStan\dumpType($o->foo); // *ERROR*
}

Seems to me like it should also resolve to int for objects, like it does for arrays, since the "undefined"/"might not exist" issue is handled as a separate error. This would also fix a related issue I encountered in a project where I'm using PHPStan.

On the other hand, an attempt to fix this revealed a test case (added in this commit) that explicitly expects an error type in a similar scenario.

So I'm not sure - is this difference between arrays and objects intentional or accidental?