Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101442
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.25.164 cause and error)
Reply-To: internals@lists.php.net
To: Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals <internals@lists.php.net>
Cc: Larry Garfield <larry@garfieldtech.com>
References: <72392123-d37b-26df-6886-218f48205f8a@fleshgrinder.com>
 <c126a971-f671-1dc8-384b-4338765996da@rhsoft.net>
 <58A5ABDF-AA25-46D4-83E7-4DE72E3DFF5E@gmail.com>
 <757270790.33iDQ9MZ2V@vulcan>
 <ff7cffc9-2941-ae84-d191-8d7da0270349@fleshgrinder.com>
 <CAF+90c9gb22sxz_CqZBg+K7is20KQkOgSP1rxgFv2m-WP76AeQ@mail.gmail.com>
Message-ID: <e5748df8-2306-5546-690c-16dd120fd4a4@fleshgrinder.com>
Date: Fri, 29 Dec 2017 18:13:08 +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: <CAF+90c9gb22sxz_CqZBg+K7is20KQkOgSP1rxgFv2m-WP76AeQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Scalar Pseudo-type
From: php@fleshgrinder.com (Fleshgrinder)

On 12/29/2017 4:37 PM, Nikita Popov wrote:
> int|float is the natural type of numeric operations in PHP. Integers
> automatically overflow into floating point numbers, so signatures using int
> in conjunction with numeric operations are somewhat problematic.
> 
> Having an explicit number type also goes well with an explicit number cast.
> PHP internally has a notion of a number cast (which is the basis for
> arithmetic operations), but currently does not expose it. As such, number
> casts currently have to be simulated using workarounds like +$x.
> 

Not sure I fully understand what you are saying.

I mean, the accuracy problem will prevail no matter what because at some
point we have to change that long to a double. The earlier the better so
users know what they are dealing with.

`+$x` seems like something that is only of interest if my source is a
string and I don't know if it should be int or float. This on the other
hand sounds like something that is happening at the edges of the
application. Or maybe you had something else in mind?

On 12/29/2017 4:37 PM, Nikita Popov wrote:
> Regarding the union type RFCs, from what I remember, one of my personal
> issues with it were the complex rules involving scalar type unions in weak
> typing mode. It's non-trivial to decide what a value should be casted to if
> it does not have the correct type. It's sort of clear what "1.5" passed to
> an int|float union becomes, but it's not intuitively obvious what should
> happen if you pass "foo" to a bool|int union, etc.
> 

Why exactly is it necessary to support weak mode together with unions
and intersections? It is obviously unclear in many situations what
should happen, so why not simply bail like in strict mode? I mean,
strict mode was added for backwards compatibility reasons. This is a new
future, there is no backwards compatibility. Anyone using it shall abide
to the strict rules of it.

-- 
Richard "Fleshgrinder" Fussenegger