rfc:mixed-typehint

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:mixed-typehint [2019/02/08 00:15]
majkl missing word
rfc:mixed-typehint [2019/02/08 00:49]
majkl typo
Line 25: Line 25:
  
 Additionally,​ as values of mixed type cannot be typehinted upon, it is not possible to achieve full native type coverage. Additionally,​ as values of mixed type cannot be typehinted upon, it is not possible to achieve full native type coverage.
- 
-The behaviour of the ''​mixed''​ type fully matches the behaviour when nothing is specified for parameter or return type (thus being implicitly mixed), effectively being an alias for previous behaviour. 
  
 ===== Mixed and Void ===== ===== Mixed and Void =====
Line 38: Line 36:
 Due to this difference, ''​void''​ is not a subtype of ''​mixed''​. Due to this difference, ''​void''​ is not a subtype of ''​mixed''​.
  
-===== Type system ​hiearchy ​=====+===== Type system ​hierarchy ​=====
  
 <​code>​ <​code>​
rfc/mixed-typehint.txt · Last modified: 2019/02/08 00:49 by majkl