Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101416
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 188.94.27.5 as permitted sender)
To: internals@lists.php.net
References: <72392123-d37b-26df-6886-218f48205f8a@fleshgrinder.com>
Reply-To: internals@lists.php.net
Message-ID: <5171148a-3554-35a3-ab72-370e1aac4a3f@php.net>
Date: Tue, 26 Dec 2017 14:38:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <72392123-d37b-26df-6886-218f48205f8a@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Scalar Pseudo-type
From: sebastian@php.net (Sebastian Bergmann)

Am 24.12.2017 um 15:34 schrieb Fleshgrinder:
> I prepared a PR to add the `scalar` pseudo-type to PHP after the
> discussions around adding a `mixed` pseudo-type. I strongly believe that
> it makes sense to provide the most common primitive union types with
> handy aliases even if we are going to add union types in the future to PHP.

Thank you, Richard, for working on this.

I spent a lot of time this year introducing scalar type declarations into
existing code bases. In quite a few cases I was not able to do so because
the existing code works with parameters that can be of two or more scalar
types. With PHP 7.2, I can only document this outside of the code using
@param annotations (until the code has been refactored to work with only
one parameter type).

With a "scalar" type declaration I would not have to fall back to @param
annotations and could express the type in actual syntax.