Property assignments follow the strict_type directive of wherever the assignment is performed from. In this case, it occurs from the ReflectionProperty::setValue() implementation, which is in strict_types=0 mode (like all extension code). Thus type coercions are allowed.

A way to perform the assignment with strict type semantics would be by using closure rebinding.

excuse my ignorance, could you give a simple example? Maybe using the case of the example script.

When you use direct assignment like $dt->name = "33"; in PHP, it performs a type check and throws an error if the type is not compatible with the property declaration. However, when you use Reflection to set a value, PHP does not perform strict type checking by default. This behavior is by design and allows you to bypass type checking when using Reflection.

If you want to enforce strict type checking even when using Reflection, you can manually enable it by calling declare(strict_types=1) inside the method that uses Reflection. Here's how you can modify the second example to throw an error if the type is not compatible:


declare(strict_types=1);

class MyClassReflection {
    public int $name;
}

$dt = new MyClassReflection();

$reflectionClass = new ReflectionClass('MyClassReflection');
$property = $reflectionClass->getProperty('name');
$property->setAccessible(true); // Make the property accessible, as it is not public
$property->setValue($dt, '33'); // Throws TypeError since '33' is a string, not an int

var_dump($dt);

(https://github.com.php)(https://www.ballsportsgames.com/how-to-choose-pickleball-paddles/)
By using declare(strict_types=1) in the scope where you are working with Reflection, you enforce strict typing for that part of the code, and setting a value of the wrong type will throw a TypeError, just like in the first example.