Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81596
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.218.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <05215ABA-DB9D-4C0A-BAAA-938FF6B0EFAB@ajf.me>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
	<B0C5801F-7D46-4CB0-9B2E-AF18C44DAF14@ajf.me>
	<54CF88BD.7050405@fischer.name>
	<05215ABA-DB9D-4C0A-BAAA-938FF6B0EFAB@ajf.me>
Date: Mon, 2 Feb 2015 18:28:09 +0200
Message-ID: <CAPhkiZyic1ebzV+hwqocUrx+o8Bxq-WP4RRcUPyk6e7S8UTHDQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Markus Fischer <markus@fischer.name>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: narf@devilix.net (Andrey Andreev)

Hi,

On Mon, Feb 2, 2015 at 6:17 PM, Andrea Faulds <ajf@ajf.me> wrote:
> Hi Markus,
>
>> On 2 Feb 2015, at 14:25, Markus Fischer <markus@fischer.name> wrote:
>>
>> - Since consensus on the strict mode does part the community (or, the
>> greater community also outside @internals) my impression is that the
>> current best way to move forward would be
>>
>> - get the rfc to only go for weak types for now
>> - using the "cast-like syntax": function foo( (int) $bar );
>>
>> and ultimately keep the strict type out for /now/ and try it at a later
>> time, the "function foo( int $bar )"-syntax.
>
> I=E2=80=99m not sure that really works that well. It=E2=80=99s not a terr=
ibly good compromise: If you want strict typing, you not only haven=E2=80=
=99t got it, but even worse, you=E2=80=99ll be forced to deal with weak typ=
ing if you use the wrong library, because the (int) syntax would be specifi=
cally for weak types. It=E2=80=99s not really a compromise at all, actually=
.
>
>> I'm actually not really in favor of just weak types, I would consider
>> myself a "strict type" voter, but through the community communication
>> here I saw a) the benefits of weak types hinting/casting b) without
>> getting in the way of a possible future strict type (e.g. with the
>> "non-cast-like syntax=E2=80=9D).
>
> Well this RFC tries to strike a different balance: rather than having the=
 chaos of some functions using weak types, others strict types, others both=
, it just adds scalar types and lets you choose the behaviour that suits yo=
u. It means weak typing fans can live in their weakly-typed world, and stri=
ct typing fans can live in their strictly-typed world. That=E2=80=99s the i=
dea, anyway.
>
> But I=E2=80=99m just going in circles at this point. :P
>

If chaos is what you call it - we want chaos. :P

Cheers,
Andrey.