Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101386 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43853 invoked from network); 19 Dec 2017 17:38:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Dec 2017 17:38:32 -0000 Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:36723] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0C/24-10479-69E493A5 for ; Tue, 19 Dec 2017 12:38:31 -0500 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3z1Q9Z6zlGzXMP for ; Tue, 19 Dec 2017 18:38:26 +0100 (CET) To: internals@lists.php.net References: <3a8054fd-b99f-771f-1f6c-29cf198acdeb@phpgangsta.de> Message-ID: <31fa8e49-18f0-f55e-beca-fe3172a78491@rhsoft.net> Date: Tue, 19 Dec 2017 18:38:26 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Mixed Typehint From: lists@rhsoft.net ("lists@rhsoft.net") 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