rfc:immutability
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:immutability [2016/08/16 19:28] – brzuchal | rfc:immutability [2018/02/20 11:19] (current) – marijic.silvio | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: Immutable classes and properties ====== | ====== PHP RFC: Immutable classes and properties ====== | ||
- | * Version: 0.1 | + | * Version: 0.2 |
- | * Date: 2016-08-12 | + | * Date: 2018-02-19 |
* Author: Michal Brzuchalski < | * Author: Michal Brzuchalski < | ||
* Author: Silvio Marijic < | * Author: Silvio Marijic < | ||
- | * Status: In Draft | + | * Status: In Discussion |
* First Published at: [[rfc: | * First Published at: [[rfc: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | This RFC proposes introduction of immutable classes and properties. Currently | + | This RFC proposes |
+ | If this mechanism is introduced, developers can be sure that they are programming with no side effects, meaning that state of the object can not be changed without developers being made aware. This is especially useful when dealing with concurrency, | ||
**Pros** | **Pros** | ||
- Immutability guaranteed by language instead of user-land implementation. | - Immutability guaranteed by language instead of user-land implementation. | ||
+ | - Programming with no side effects. | ||
- Safe for concurrency. | - Safe for concurrency. | ||
- Value objects, DTO's etc. can be easily created. | - Value objects, DTO's etc. can be easily created. | ||
- | - Properties can be public which removes need for getters without allowing state modification. | + | - Properties can be public which removes |
- (Please point it out more advantages) | - (Please point it out more advantages) | ||
**Cons** | **Cons** | ||
- | - Cloning has to be disabled for immutable | + | - Currently arrays on immutable |
- | - (Please point it out more disadvantages) | + | |
- | **Before** | + | ===== Proposal ===== |
+ | |||
+ | ==== Immutable Class ==== | ||
+ | |||
+ | A class defined as immutable will imply immutability across all of its properties by default. After the object is constructed, | ||
<code php> | <code php> | ||
- | <?php | ||
- | class Email { | + | immutable |
- | | + | |
public function __construct ($email) { | public function __construct ($email) { | ||
- | | + | |
+ | } | ||
+ | } | ||
- | | + | $email = new Email(" |
+ | $email-> | ||
+ | |||
+ | </ | ||
+ | |||
+ | Changes to inheritance are made to add constraints when extending an immutable class - the child class must also be immutable in order to preserve immutability across the whole object. | ||
+ | |||
+ | <code php> | ||
+ | immutable class Foo{} | ||
+ | class Bar extends Foo{} // Will result in Fatal Error | ||
+ | </ | ||
+ | |||
+ | |||
+ | ==== Immutable Properties ==== | ||
+ | |||
+ | Classes have the ability to enforce immutability to only a subset of properties if needed, in that case, immutability will be implied only on properties that are declared as immutable. | ||
+ | |||
+ | <code php> | ||
+ | class User { | ||
+ | private $id; | ||
+ | public immutable $email; | ||
+ | |||
+ | public function __construct ($id, $email) { | ||
+ | $this-> | ||
+ | | ||
} | } | ||
+ | } | ||
+ | </ | ||
- | | + | |
- | return | + | If an immutable property contains an object, to preserve immutability, |
+ | <code php> | ||
+ | immutable class Email{} | ||
+ | |||
+ | class User { | ||
+ | public immutable $email; | ||
+ | |||
+ | | ||
+ | $this->email = $email; | ||
} | } | ||
} | } | ||
</ | </ | ||
- | **After** | + | Resources are not allowed to be assigned to immutable properties because of fact that resources by nature are not immutable. |
<code php> | <code php> | ||
- | <?php | + | class File { |
+ | public immutable $handle; | ||
+ | public function __construct ($handle) { | ||
+ | $this-> | ||
+ | } | ||
+ | } | ||
+ | |||
+ | $file = new File(fopen(' | ||
+ | </ | ||
+ | |||
+ | Arrays are not allowed to be assigned to immutable properties.. | ||
+ | <code php> | ||
+ | class A { | ||
+ | public immutable $x; | ||
+ | |||
+ | public function __construct ($x) { | ||
+ | $this->x = $x; | ||
+ | } | ||
+ | } | ||
+ | |||
+ | $a = new A([' | ||
+ | </ | ||
+ | |||
+ | If an immutable property of a parent class is overridden in a child class, it has to be declared as immutable. | ||
+ | Since the focus of this RFC is immutable objects, having static properties in immutable classes will result in a compile error. | ||
+ | |||
+ | |||
+ | ==== References ==== | ||
+ | |||
+ | Assigning by references to immutable properties will result in an error, otherwise the object loses control over properties, and immutability can be broken. | ||
+ | |||
+ | <code php> | ||
immutable class Email { | immutable class Email { | ||
public $email; | public $email; | ||
Line 56: | Line 128: | ||
} | } | ||
} | } | ||
+ | |||
+ | $email = new Email(" | ||
+ | $emailRef = & | ||
+ | $emailRef = " | ||
+ | </ | ||
+ | |||
+ | ==== Comparison ==== | ||
+ | |||
+ | Identity of immutable object is based on its value. So two immutable are identical if they are of the same type and contain same value. | ||
+ | |||
+ | <code php> | ||
+ | immutable class Email { | ||
+ | public $email; | ||
+ | |||
+ | public function __construct ($email) { | ||
+ | // validation | ||
+ | |||
+ | $this-> | ||
+ | } | ||
+ | } | ||
+ | |||
+ | $email1 = new Email(" | ||
+ | $email2 = new Email(" | ||
+ | var_dump($email1 === $email2); // bool(true) | ||
</ | </ | ||
===== Examples ===== | ===== Examples ===== | ||
- | Money Pattern, defined by Martin Fowler and published in Patterns of Enterprise Application Architecture, | + | Notice in above example, changing getters and setters methods to public properties is optional. They simply don't need to be protected anymore, in fact, immutable class objects are deeply frozen with exceptions on write. |
+ | |||
+ | Every example shows where internal object state is important. Any references to objects passed into an immutable class constructor cannot be references to scalars or may be immutable class instances. That gives high guarantee you will keep internal state unchanged for all the time. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | ==== Money ==== | ||
+ | |||
+ | Money Pattern, defined by Martin Fowler and published in Patterns of Enterprise Application Architecture, | ||
<code php> | <code php> | ||
Line 193: | Line 298: | ||
</ | </ | ||
- | There is no need for getters because internally immutable object | + | There is no need for getters because |
- | + | ||
- | + | ||
- | ===== Proposal ===== | + | |
- | + | ||
- | Class defined as immutable will imply immutability across all of it's properties by default. After constructor returns, it will not be possible to modify state of immutable properties from any scope. | + | |
- | + | ||
- | <code php> | + | |
- | + | ||
- | immutable class Email { | + | |
- | public $email; | + | |
- | + | ||
- | public function __construct ($email) { | + | |
- | // validation | + | |
- | + | ||
- | $this-> | + | |
- | } | + | |
- | } | + | |
- | + | ||
- | $email = new Email(" | + | |
- | $email-> | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | Regular classes can define immutability per property. | + | |
- | + | ||
- | <code php> | + | |
- | class Email { | + | |
- | public immutable $email; | + | |
- | + | ||
- | public function __construct ($email) { | + | |
- | // validation | + | |
- | + | ||
- | $this-> | + | |
- | } | + | |
- | } | + | |
- | + | ||
- | $email = new Email(" | + | |
- | $email-> | + | |
- | </ | + | |
- | + | ||
- | Any class that extends immutable class must be also declared as immutable. | + | |
- | + | ||
- | <code php> | + | |
- | immutable class Foo{} | + | |
- | class Bar extends Foo{} // Will result in Fatal Error | + | |
- | </ | + | |
- | + | ||
- | + | ||
- | It will not be possible to assign value by reference to immutable property. | + | |
- | <code php> | + | |
- | immutable class Email { | + | |
- | public $email; | + | |
- | + | ||
- | public function __construct ($email) { | + | |
- | // validation | + | |
- | + | ||
- | $this-> | + | |
- | } | + | |
- | } | + | |
- | + | ||
- | $email = new Email(" | + | |
- | $emailRef = & | + | |
- | $emailRef = " | + | |
- | </ | + | |
- | + | ||
- | If immutable property contains object, object must also be an instance of immutable class. | + | |
- | + | ||
- | <code php> | + | |
- | + | ||
- | class Bar{} | + | |
- | + | ||
- | immutable class Foo { | + | |
- | public $bar; | + | |
- | + | ||
- | public function __construct (Bar $bar) { | + | |
- | // validation | + | |
- | + | ||
- | $this-> | + | |
- | } | + | |
- | } | + | |
- | + | ||
- | $foo = new Foo(new Bar()); // Will result in a error because Bar is not instance of immutable class | + | |
- | </ | + | |
===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
- | No backward | + | No backwardly |
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== | ||
- | - PHP 7.2 | + | To be discussed. |
===== RFC Impact ===== | ===== RFC Impact ===== | ||
Line 295: | Line 317: | ||
==== To Existing Extensions ==== | ==== To Existing Extensions ==== | ||
- | - Reflection. | + | - Reflection |
==== To Opcache ==== | ==== To Opcache ==== | ||
Line 317: | Line 339: | ||
===== Future Scope ===== | ===== Future Scope ===== | ||
+ | Add support for arrays on immutable properties. | ||
+ | Expand immutability to regular variables also. | ||
===== Proposed Voting Choices ===== | ===== Proposed Voting Choices ===== | ||
Line 324: | Line 348: | ||
===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
- | + | [[https:// | |
Line 335: | Line 358: | ||
===== References ===== | ===== References ===== | ||
- | |||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
+ | - Immutable interfaces |
rfc/immutability.1471375730.txt.gz · Last modified: 2017/09/22 13:28 (external edit)