Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95995
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.15 as permitted sender)
To: "David (Dj) Eddy" <pheagey@gmail.com>, internals@lists.php.net
References: <CA+474t8TXe--nxwkp6OU3ALj91McX6BCs9=+4eCjsCq4N5GFFg@mail.gmail.com>
Message-ID: <4f95c850-d7c2-a3c2-6114-f5f858da395e@gmx.de>
Date: Wed, 14 Sep 2016 18:03:50 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CA+474t8TXe--nxwkp6OU3ALj91McX6BCs9=+4eCjsCq4N5GFFg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Concept: 7.1 nullable function parameter format ...
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 14.09.2016 at 17:10, David (Dj) Eddy wrote:

> Issue: Currently the format for nullable function parameters is as
> follows: `fn(?int $param)`; this makes little visual sense from an
> outside perspective. What does the `?` mean? PHP does not have a `?`
> data type; it is very visually ambiguous.
> 
> Suggestion: `fn(null|int $param)`. This uses the same syntax format
> that other logic constructs in the language use as well as being very
> explicit to the data types allowed for the parameter. For the moment
> only `null|{one other data type}` would be the goal of the RFC;
> however in future iterations multiple data types could be allowed.
> 
> Gauge initial interest in a alteratio of this type, thanks for your time.

There has already been the union type RFC[1], which has recently been
declined.

[1] <https://wiki.php.net/rfc/union_types>

-- 
Christoph M. Becker