rfc:mixed-typehint

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:mixed-typehint [2019/02/07 23:48] – improved version with better language and variance rules majklrfc:mixed-typehint [2019/02/08 00:28] – removed obsolete statement majkl
Line 22: Line 22:
   - the value is of specific type, but the native type was forgotten.   - the value is of specific type, but the native type was forgotten.
  
-At the time of writing it is not possible between the abovementioned scenarios.+At the time of writing it is not possible to differentiate between the abovementioned scenarios.
  
 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 =====
rfc/mixed-typehint.txt · Last modified: 2020/07/22 09:03 by kocsismate