Re: [RFC] Mixed Typehint
| From: | lists@rhsoft.net | Date: | Tue, 19 Dec 2017 17:38:26 +0000 |
| Subject: | Re: [RFC] Mixed Typehint | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-101386@lists.php.net to get a copy of this message | ||
Am 19.12.2017 um 18:30 schrieb Levi Morrison:
In any case we are straying off-topic: this thread is about mixed
which I would vote against. As our type-system stands it provides
almost no value. If our type system ever changes and it suddenly
provides value then it should be proposed at that point
IMHO the wrong question, the right ones would be
a) how much work is it to implement
b) does it any harm
c) is it maintainable and does it bring relevant maintainance cost
the fact that in a sane project where you use typehints wherever it is possible that you then can distinct between forgotten typehint versus explicit statet brings a benefit for userland code while nobody is forced to use it