Please note something:
The docs explain clearly that this method is called when "isset()" or "empty()" are called on the object's key.
This means that there is a huge difference in your custom implementation when you have an internal array on which you choose to call either "isset()" or "array_key_exists()".
Even though the method says "offsetExists", it is *not* supposed to be used only when the offset exists, because this is not at all the behavior of neither "isset" nor "empty" internally.
This means you can have issues like this (more explanations below):
<?php
class Value {
public function __construct(
public string $value,
) {
}
}
class MyArray implements ArrayAccess {
private array $internal = [];
public function offsetExists(mixed $offset): bool
{
return array_key_exists($offset, $this->internal);
}
public function offsetGet(mixed $offset): mixed
{
return $this->offsetExists($offset) ? $this->internal[$offset] : null;
}
public function offsetSet(mixed $offset, mixed $value): void
{
if (is_null($offset)) {
$this->internal[] = $value;
} else {
$this->internal[$offset] = $value;
}
}
public function offsetUnset(mixed $offset): void
{
unset($this->internal[$offset]);
}
}
$object = new MyArray();
$object['key'] = null;
$otherValue = isset($object['key']) ? new Value($object['key']) : null;
?>
The thing here is that we have some code that cannot use the "??" operator because we need the output of the "isset" call to return true, and only then we want to use.
With a real array, this should be fairly common because we know how "isset" works.
However, since the "offsetExists" method has a lot of different implementations in PHP libaries, you should *not* trust the output in "isset" with objects implementing ArrayAccess.
A workaround is to create an intermediate variable and run "isset()" on it:
<?php
$otherValue = isset($arrayObject['key']) ? new Value($arrayObject['key']) : null;
$rawValue = $arrayObject['key'] ?? null;
$otherValue = isset($rawValue) ? new Value($rawValue) : null;
?>