Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101374
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.45 as permitted sender)
To: Michael Moravec <php.net@majkl578.cz>, internals@lists.php.net
References: <CAO7eTqNQ5T7=9pYC_q35ETnBDzNwEeSjvuvvv_uy3+LmEjcovw@mail.gmail.com>
Message-ID: <a3f0e7dd-0afe-b44e-80ba-489e0f2b6ddd@gmail.com>
Date: Mon, 18 Dec 2017 22:32:58 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAO7eTqNQ5T7=9pYC_q35ETnBDzNwEeSjvuvvv_uy3+LmEjcovw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Mixed Typehint
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I'd like to propose and discuss Mixed Typehint RFC for PHP 7.3:
> https://wiki.php.net/rfc/mixed-typehint
> 
> The purpose of this RFC is to introduce "mixed" typehint on language level
> to be used
> as a valid typehint. PHP currently forces users to not use any type in case
> the
> type is mixed/unclear. This makes code inconsistent and less explicit. With

I'm not sure what's the point of it. "mixed" means "any type". Not
writing a type means "any type". So why waste space and add something
that contributes nothing when everybody is already using the current
convention and the new one does not add anything at all?

> mixed,
> it should be easy to eliminate this inconsistency 

There's no "inconsistency" here.

> and achieve fully type hinted code.

This is not an "achievement" - adding prefixes for the sake of all
variables having prefixes that mean nothing is not an "achievement". I
do not see any point in it.
-- 
Stas Malyshev
smalyshev@gmail.com