Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101402 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 933 invoked from network); 20 Dec 2017 12:56:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Dec 2017 12:56:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=sebastian@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sebastian@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 188.94.27.5 as permitted sender) X-PHP-List-Original-Sender: sebastian@php.net X-Host-Fingerprint: 188.94.27.5 scarlet.netpirates.net Received: from [188.94.27.5] ([188.94.27.5:54642] helo=scarlet.netpirates.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EB/9A-10479-20E5A3A5 for ; Wed, 20 Dec 2017 07:56:38 -0500 Received: (qmail 12676 invoked by uid 89); 20 Dec 2017 12:56:32 -0000 Received: by simscan 1.4.0 ppid: 12668, pid: 12671, t: 0.0971s scanners: attach: 1.4.0 clamav: 0.99.1/m:/d:20700 Received: from unknown (HELO ?192.168.178.93?) (php@sebastian-bergmann.de@217.229.40.253) by scarlet.netpirates.net with ESMTPA; 20 Dec 2017 12:56:32 -0000 To: internals@lists.php.net References: Reply-To: internals@lists.php.net Message-ID: Date: Wed, 20 Dec 2017 13:56:30 +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: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Mixed Typehint From: sebastian@php.net (Sebastian Bergmann) On 12/19/2017 04:34 AM, Michael Moravec wrote: > I'd like to propose and discuss Mixed Typehint RFC for PHP 7.3: > https://wiki.php.net/rfc/mixed-typehint "mixed" is too unspecific. I understand the reasoning behind wanting "mixed": to express explicitly that a type declaration was not forgotten. I think that a "scalar" type that "groups together" bool, float, int, and string would make more sense. This would allow the expression that something is not an array, not an object, and not a resource.