Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81106
Return-Path: <smalyshev@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 34254 invoked from network); 25 Jan 2015 04:14:50 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Jan 2015 04:14:50 -0000
Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.179 as permitted sender)
X-PHP-List-Original-Sender: smalyshev@gmail.com
X-Host-Fingerprint: 209.85.192.179 mail-pd0-f179.google.com  
Received: from [209.85.192.179] ([209.85.192.179:54570] helo=mail-pd0-f179.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 62/83-11456-9BD64C45 for <internals@lists.php.net>; Sat, 24 Jan 2015 23:14:49 -0500
Received: by mail-pd0-f179.google.com with SMTP id v10so5566921pde.10
        for <internals@lists.php.net>; Sat, 24 Jan 2015 20:14:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=s8+iv2nzI6N5WN3htmzhTeZups30HBc2eMhhhex3J1Q=;
        b=v9HDRw93oe2w/yipSL3QPmX6U8Ks4Id13fuAM6QFcGFm5ZrV6CQmXX9Do4qy/aIil/
         j+37kn5+9ItYT1QdBh/xfbzzsWn3eLGf1GWaRtTDDQiC3bJryWfzG3TbfGtR9QwsojkL
         FmSLgVaRMsj9WT6Uu34uIs5yBvqcjIoSnGmNqH/LtQTyXVMQXaaNUShYoDmcsM2cVpKd
         o0OnFtjXkpEPbKmBIzEAQoS7LDjJdAPMYNM0tGZFBHz7R/I/i/Ny0MtOKvgs1SyBf329
         ECFb+WnbNhWT1vrlx/YF58Um0ND3n1d1F3I484e6FaDmBpcpOrkxOLElWgcAW9E5HL+F
         HFAA==
X-Received: by 10.68.69.3 with SMTP id a3mr23809247pbu.3.1422159286672;
        Sat, 24 Jan 2015 20:14:46 -0800 (PST)
Received: from [192.168.2.145] (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48])
        by mx.google.com with ESMTPSA id bx13sm6152390pdb.19.2015.01.24.20.14.45
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Sat, 24 Jan 2015 20:14:45 -0800 (PST)
Message-ID: <54C46DB4.2090406@gmail.com>
Date: Sat, 24 Jan 2015 20:14:44 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Andrea Faulds <ajf@ajf.me>, PHP Internals <internals@lists.php.net>
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <90B1885A-E767-484E-8F38-A791E8A3FE9B@ajf.me>
In-Reply-To: <90B1885A-E767-484E-8F38-A791E8A3FE9B@ajf.me>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> going to a vote. That said, I do lean towards always strict, given
> you can usually ensure your return type’s correct.

Wait, so we would have two modes, strict and non-strict, but also in
non-strict mode, return types still will be strict? Yay, consistency!

-- 
Stas Malyshev
smalyshev@gmail.com