rfc:readonly_properties_v2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
rfc:readonly_properties_v2 [2021/06/04 16:15] – nikicrfc:readonly_properties_v2 [2021/07/01 10:16] – nikic
Line 2: Line 2:
   * Date: 2021-06-02   * Date: 2021-06-02
   * Author: Nikita Popov <nikic@php.net>   * Author: Nikita Popov <nikic@php.net>
-  * Status: Draft+  * Status: Voting
   * Target Version: PHP 8.1   * Target Version: PHP 8.1
   * Implementation: https://github.com/php/php-src/pull/7089   * Implementation: https://github.com/php/php-src/pull/7089
Line 77: Line 77:
 class Test { class Test {
     public function __construct(     public function __construct(
-        public readonly int $prop = 0,+        public readonly int $i = 0, 
 +        public readonly array $ary = [],
     ) {}     ) {}
 } }
  
 $test = new Test; $test = new Test;
-$test->prop += 1; +$test->i += 1; 
-$test->prop++; +$test->i++; 
-++$test->prop; +++$test->i; 
-$ref =& $test->prop; +$test->ary[] = 1; 
-$test->prop =& $ref; +$test->ary[0][] = 1; 
-byRef($test->prop);+$ref =& $test->i; 
 +$test->i =& $ref; 
 +byRef($test->i);
 foreach ($test as &$prop); foreach ($test as &$prop);
 </PHP> </PHP>
Line 261: Line 264:
  
 ''ReflectionProperty::setValue()'' can bypass the requirement that initialization occurs from the scope where the property has been declared. However, reflection cannot modify a readonly property that has already been initialized. ''ReflectionProperty::setValue()'' can bypass the requirement that initialization occurs from the scope where the property has been declared. However, reflection cannot modify a readonly property that has already been initialized.
 +
 +Similarly, closure rebinding can be used to bypass the initialization scope requirement.
 +
 +==== Serialization ====
 +
 +Readonly properties have no impact on serialization. As ''%%__unserialize()%%'' (and the legacy ''Serializable::unserialize()'') method are invoked without a prior constructor call, readonly properties will be in an uninitialized state and can be set by the ''%%__unserialize()%%'' implementation.
 +
 +This also applies to userland serializers and hydrators. As long as the object is created using ''ReflectionClass::newInstanceWithoutConstructor()'' or some other constructor-bypass, it is always safe to initialize readonly properties.
  
 ===== Rationale ===== ===== Rationale =====
Line 331: Line 342:
 ===== Vote ===== ===== Vote =====
  
-Yes/No.+Voting started on 2021-07-01 and closes on 2021-07-15. 
 + 
 +<doodle title="Add readonly properties as proposed?" auth="nikic" voteType="single" closed="false"> 
 +   * Yes 
 +   * No 
 +</doodle>
  
rfc/readonly_properties_v2.txt · Last modified: 2021/07/20 15:37 by nikic

Page Tools