Differences

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

--- rfc:mixed_type_v2 [2020/04/20 01:12] – danack
+++ rfc:mixed_type_v2 [2020/04/20 11:20] – danack
@@ Line 4: / Line 4: @@
   * Author: Máté Kocsis <kocsismate@php.net>, Danack<danack@php.net>
   * Based on previous RFC by: Michael Moravec
-  * Target Version: 8.0
+  * Status: Under discussion
-  * Status: In Draft
+  * Implementation: https://github.com/php/php-src/pull/5313
-  * Implementation:
   * First Published at: https://wiki.php.net/rfc/mixed_type_v2
 ===== Introduction =====
-With the addition of scalar types in PHP 7, nullables in 7.1, `object` in 7.2, and lastly, union types in 8.0, people writing PHP code can explicitly declare type information for most function parameters, function returns, as well as class properties.
+With the addition of scalar types in PHP 7, nullables in 7.1, object in 7.2, and lastly, union types in 8.0, people writing PHP code can explicitly declare type information for most function parameters, function returns, as well as class properties.
 However, PHP has not always supported types, and most probably it will always allow to omit type information. But this leads to the problem that its meaning is ambiguous when type information is missing:
@@ Line 295: / Line 294: @@
 ===== Backward Incompatible Changes =====
-Since PHP 7.0, ''mixed'' is a 'soft' reserved word.
+Since PHP 7.0, ''mixed'' is a 'soft' reserved word. This RFC would prevent the use of ''mixed'' as a class name if it is passed.
 ===== To SAPIs =====