Hi, internals!
Since writing Asymmetric visibility Reflection API problems - Externals I've realized that
the major problem with aviz is actually simple but fundamental.
In PHP <=8.0 this code is valid for an object of any user class:
class User
{
public string $name = 'Bob';
}
$object = new User();
foreach ($object as $property => $value) {
$object->{$property} = 'Jack';
}
The same is true for Reflection API: once you check that `(new
ReflectionProperty(Foo::class, 'property'))->isPublic()`, you can
safely read property and write to it from any scope.
Now let's jump to PHP 8.1+ with support for readonly properties.
A readonly property is two functionalities in one: write-once and
private set. This means that `public readonly $property` is actually
`public(get) private(set) readonly $property`. Although it is marked
as `public`, it is not public because it is not a symmetric public
property!
In PHP 8.1+, the following User class suddenly breaks the code above:
class User
{
public function __construct(
public readonly string $name = 'Bob',
) {}
}
$object = new User();
foreach ($object as $property => $value) {
// Fatal error: Uncaught Error: Cannot modify readonly property User::$name
$object->{$property} = 'Jack';
}
In other words, the meaning of `public` has changed in PHP 8.1.
Before, it used to mean "symmetric", now it means "symmetric unless
readonly".
While not explicitly stated in changelogs, this was a BC break,
because a changed semantic of smth that existed before is a BC break.
Did it break anything? Of course it did! See:
- PHP readonly properties and inheritance cause error on hydration · Issue #10049 · doctrine/orm · GitHub
- [ExpressionLanguage] Revert readonly flag on ConstantNode::$isNullSafe by fmata · Pull Request #46840 · symfony/symfony · GitHub
- Cannot hydrate readonly properties · Issue #656 · Ocramius/GeneratedHydrator · GitHub
- Is there a workaround serializing readonly properties? · Issue #129 · opis/closure · GitHub
I believe there are still many places where the concept of "public"
needs to be adjusted to fully support readonly properties.
Now in PHP 8.4 asymmetry will be made explicit and will allow users to
specify visibility for setters. However, the core issue remains
unresolved:
final class User
{
public function __construct(
public private(set) string $name = 'Bob',
) {}
}
$object = new User();
foreach ($object as $property => $value) {
// Fatal error: Uncaught Error: Cannot modify private(set)
property User::$name from global scope
$object->{$property} = 'Jack';
}
I'd like to draw your attention to the fact that aviz introduces a BC
break, despite saying "Backward Incompatible Changes: None. This
syntax would have been a parse error before." While the syntax is new,
it allows one to alter the old concept of public by changing set
visibility.
What can we do about it:
1. Explicitly introduce the concept of getter and setter visibility,
preserve `ReflectionProperty::isPublic()` behavior from PHP <=8.0 and
add `ReflectionProperty::(get|set)Is(Public|Protected|Private)`
methods. I have explained all these ideas in
Asymmetric visibility Reflection API problems - Externals . If this option is chosen, aviz
will likely need to be reverted and reintroduced in PHP 8.5, since
we're already in the feature freeze period.
2. Proceed with the current approach, but clearly explain the BC break
in the changelog, and merge this PR
Implement ReflectionProperty::is{Readable,Writable}() by iluuu1994 · Pull Request #16209 · php/php-src · GitHub to mitigate reflection
issues as outlined in Asymmetric visibility Reflection API problems - Externals.
--
Best regards,
Valentin
Thank you for your interest!