rfc:immutability
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:immutability [2016/08/16 19:47] – brzuchal | rfc:immutability [2016/12/02 14:54] – marijic.silvio | ||
---|---|---|---|
Line 9: | Line 9: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | This RFC proposes introduction of immutable classes and properties. Currently | + | This RFC proposes introduction of immutable classes and properties. Currently |
+ | If those mechanizsm is utilized, developer can be sure that he is programming with no side effects, meaning that state of the object can not be changed with developer beeing unaware of that. This especialy comes hand in hand with concurrency when we can guarantee that threads will always read the same value. | ||
**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. | ||
Line 20: | Line 22: | ||
**Cons** | **Cons** | ||
- | - Cloning has to be disabled for immutable objects | ||
- (Please point it out more disadvantages) | - (Please point it out more disadvantages) | ||
- | **Before** | + | ===== Proposal ===== |
- | <code php> | + | |
- | <?php | + | |
- | class Email { | + | ==== Immutable Class ==== |
- | private $_email; | + | |
- | public function __construct ($email) { | + | Class defined as immutable will imply immutability across all of it's properties by default. After object is constructor, |
- | // validation | + | |
- | $this-> | ||
- | } | ||
- | |||
- | public function getValue() { | ||
- | | ||
- | } | ||
- | } | ||
- | </ | ||
- | |||
- | **After** | ||
<code php> | <code php> | ||
- | <?php | ||
immutable class Email { | immutable class Email { | ||
Line 51: | Line 37: | ||
public function __construct ($email) { | public function __construct ($email) { | ||
- | // validation | ||
- | |||
$this-> | $this-> | ||
} | } | ||
} | } | ||
+ | |||
+ | $email = new Email(" | ||
+ | $email-> | ||
+ | |||
</ | </ | ||
- | ===== Proposal ===== | + | Changes to inheritance are made to add constraints when extending a immutable |
- | + | ||
- | Class defined as immutable | + | |
<code php> | <code php> | ||
+ | immutable class Foo{} | ||
+ | class Bar extends Foo{} // Will result in Fatal Error | ||
+ | </ | ||
- | immutable class Email { | ||
- | public $email; | ||
- | | + | ==== Immutable Properties ==== |
- | // validation | + | |
+ | Classes have ability to enforce immutability to only subset of properties if needed, in that case immutability will be implied only on properties that are delared immutable. | ||
+ | |||
+ | <code php> | ||
+ | class User { | ||
+ | private $id; | ||
+ | | ||
+ | public function __construct ($id, $email) { | ||
+ | $this-> | ||
$this-> | $this-> | ||
} | } | ||
} | } | ||
- | |||
- | $email = new Email(" | ||
- | $email-> | ||
- | |||
</ | </ | ||
- | Regular classes can define immutability per property. | ||
+ | If immutable property contains object, to preserve immutability, | ||
<code php> | <code php> | ||
- | class Email { | + | immutable |
+ | |||
+ | class User { | ||
public immutable $email; | public immutable $email; | ||
- | public function __construct ($email) { | + | public function __construct (Email $email) { |
- | // validation | + | |
$this-> | $this-> | ||
} | } | ||
} | } | ||
+ | </ | ||
- | $email = new Email(" | + | Resources are not allowed to be assigned to immutable properties because of fact that resources by nature are not immutable. |
- | $email->email = " | + | <code php> |
+ | class File { | ||
+ | public immutable | ||
+ | |||
+ | public function __construct | ||
+ | $this->handle | ||
+ | } | ||
+ | } | ||
+ | |||
+ | $file = new File(fopen(' | ||
</ | </ | ||
- | Any class that extends | + | If immutable |
+ | Since focus of this RFC is on immutable objects, having static properties in immutable classes will result in compile error. | ||
- | <code php> | ||
- | immutable class Foo{} | ||
- | class Bar extends Foo{} // Will result in Fatal Error | ||
- | </ | ||
+ | ==== References ==== | ||
+ | |||
+ | Assigning by references to immutable properties will result with error, otherwise object looses controll over properties and immutability can be broken. | ||
- | It will not be possible to assign value by reference to immutable property. | ||
<code php> | <code php> | ||
immutable class Email { | immutable class Email { | ||
Line 121: | Line 121: | ||
</ | </ | ||
- | If immutable property contains object, object must also be an instance of immutable class. | ||
- | <code php> | + | ===== Examples ===== |
+ | Notice in above examples removing getters and setting properties to public is optional. They simply doesn' | ||
- | class Bar{} | + | Every example shows where internal object state is important. Any references to objects passed into immutable |
- | 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 | ||
- | </ | ||
- | |||
- | |||
- | ===== Examples ===== | ||
==== Money ==== | ==== Money ==== | ||
Line 280: | Line 267: | ||
There is no need for getters because internally immutable object if deeply frozen and none of his properties cannot be written anymore. All properties accepts scalar values or objects which implements immutable classes so there is high guarantee such Money object will keep his internal state untouched. | There is no need for getters because internally immutable object if deeply frozen and none of his properties cannot be written anymore. All properties accepts scalar values or objects which implements immutable classes so there is high guarantee such Money object will keep his internal state untouched. | ||
- | |||
- | ==== URI ==== | ||
Line 300: | Line 285: | ||
==== To Existing Extensions ==== | ==== To Existing Extensions ==== | ||
- | - Reflection. | + | - Reflection |
==== To Opcache ==== | ==== To Opcache ==== | ||
Line 329: | Line 314: | ||
===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
- | + | [[https:// | |
Line 340: | Line 324: | ||
===== References ===== | ===== References ===== | ||
- | |||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
+ | - Immutable interfaces |
rfc/immutability.txt · Last modified: 2018/02/20 11:19 by marijic.silvio