Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127545
Message-ID: <0ac00d42-7584-4de2-bca4-9099f3d4cbb5@sandfox.me>
Date: Tue, 3 Jun 2025 04:34:09 +0300
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Transform void into an alias for null
To: internals@lists.php.net
References: <6Z2Ysh6MjYp1nyzuB0bTPJc5srObIcMRqt731JaQeXUJk1f_V_Yo2nRn8WvjI7er7pp7pIUE6WYl5pRwvYrtcrd07nCutyAqKPSsZHmrS-Y=@gpb.moe>
 <7f7dc3dc-bb9a-4f6e-9b77-055c4a8801d1@rwec.co.uk>
Content-Language: en-US
In-Reply-To: <7f7dc3dc-bb9a-4f6e-9b77-055c4a8801d1@rwec.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: sandfox@sandfox.me (Anton Smirnov)

On 02/06/2025 23:50, Rowan Tommins [IMSoP] wrote:
> I agree the type hierarchy you describe is weird, but rather than 
> throwing away the functionality completely, I wonder if we can make it 
> more consistent:
> 
> - Make "no return type declared" and "mixed" equivalent
> - Make "void" a sub-type of "null", and therefore a sub-type of "mixed"

I think that null and void are semantically very different so I'd like 
to suggest just making void subtype of mixed. This will both keep the 
semantic meaning of void and make mixed and undeclared mean the same thing.

-- 
Anton