Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109718
User-Agent: Cyrus-JMAP/3.1.7-1152-g08c8976-fmstable-20200420v1
Mime-Version: 1.0
Message-ID: <bbab0dfc-969c-451c-836b-77a17f176be6@www.fastmail.com>
In-Reply-To: 
 <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
References: 
 <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
Date: Mon, 20 Apr 2020 08:51:51 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] [RFC] Mixed type
From: larry@garfieldtech.com ("Larry Garfield")

On Mon, Apr 20, 2020, at 6:17 AM, Dan Ackroyd wrote:
> Hi Internals,
> 
> Here is an RFC for adding a 'mixed' type to the language:
> https://wiki.php.net/rfc/mixed_type_v2
> The RFC builds on an earlier draft by Michael Moravec.
> 
> Part of the motivation for pursuing this RFC was my recent experience
> in upgrading an application to PHP 7.4.
> 
> Being able to add types to the application made the code much easier
> to reason about, but there were places where I couldn't add type info
> due to the lack of mixed. That made it hard to see if that piece of
> code had been upgraded (but type info couldn't be added), or if that
> code still needed to be upgraded.
> 
> cheers
> Dan
> Ack

I am not against this, but now that we have Union types what places are there where the currently available type declarations are insufficient?  Resource seems like the only remaining gap where you'd be forced to use `mixed` instead of a union.

--Larry Garfield