Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80077
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 2792 invoked from network); 2 Jan 2015 00:52:49 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 2 Jan 2015 00:52:49 -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.218.47 as permitted sender)
X-PHP-List-Original-Sender: smalyshev@gmail.com
X-Host-Fingerprint: 209.85.218.47 mail-oi0-f47.google.com  
Received: from [209.85.218.47] ([209.85.218.47:42447] helo=mail-oi0-f47.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id BA/04-18015-0EBE5A45 for <internals@lists.php.net>; Thu, 01 Jan 2015 19:52:48 -0500
Received: by mail-oi0-f47.google.com with SMTP id v63so39232137oia.6
        for <internals@lists.php.net>; Thu, 01 Jan 2015 16:52: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:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        bh=OtwLYAlch56+5nmOC00CwBVY23gQxTHQBGRcnK1cByw=;
        b=PnDvG/h92cI2k94pFEQMANFo3FpIAdEIGFRxZIbZ/ITMsRKO247RHd9lUkd/ThL2Ny
         ujZNjmqebRo8QRPZTNtJpOUcmNuw8FctYx1xt9LupJ9NPBC7yQtXVtHnPYiZsu8QG0gC
         h26IYmOUfvLXPAg/6IabhHoUXmUX/Ue88PWWfxUZNjM9ZBAxvKe1Mu8jErKuZI6buCMW
         wy2VCo2CTiWZJC9ZhiVD9uZk5pCFgyOcW2wjzumw+R4rl5g915cFCmYqm0EEHsUkKvTX
         U5u6Moa987QCWbLlKISaPUzrpKCvRMZcAo2y9zLx43RtoklGMqiQ64yZunx/fqWuHUrj
         wKog==
X-Received: by 10.60.146.231 with SMTP id tf7mr523097oeb.48.1420159965992;
        Thu, 01 Jan 2015 16:52:45 -0800 (PST)
Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48])
        by mx.google.com with ESMTPSA id y15sm24206347oia.20.2015.01.01.16.52.45
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 01 Jan 2015 16:52:45 -0800 (PST)
Message-ID: <54A5EBD5.2070905@gmail.com>
Date: Thu, 01 Jan 2015 16:52:37 -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>
CC: PHP Internals <internals@lists.php.net>
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <54A466CB.9020400@gmail.com> <F4EB5BF5-E9B3-42C5-9291-88CB42A29207@ajf.me> <54A5E309.4050109@gmail.com> <47A3057F-4C2C-4059-864F-EC8912F3D17D@ajf.me>
In-Reply-To: <47A3057F-4C2C-4059-864F-EC8912F3D17D@ajf.me>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> If they were case-sensitive, this would be inconsistent with other type names like array and callable.

Of course, I mean making all these hints case-sensitive. I have never
seen code using uppercase Callable or Array, though I imagine it might
happen. Github's search is case-insensitive so I don't really know how
to check for it - though since I see absolutely no reason for doing that
(no documentation, examples, guides, best practices, etc. ever suggest
you should write Callable) I would guesstimate the impact would be small.
-- 
Stas Malyshev
smalyshev@gmail.com