Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80064
Return-Path: <morrison.levi@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 61457 invoked from network); 1 Jan 2015 17:19:54 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 1 Jan 2015 17:19:54 -0000
Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.169 as permitted sender)
X-PHP-List-Original-Sender: morrison.levi@gmail.com
X-Host-Fingerprint: 209.85.214.169 mail-ob0-f169.google.com  
Received: from [209.85.214.169] ([209.85.214.169:52595] helo=mail-ob0-f169.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 1C/F0-60454-9B185A45 for <internals@lists.php.net>; Thu, 01 Jan 2015 12:19:53 -0500
Received: by mail-ob0-f169.google.com with SMTP id vb8so51353600obc.0
        for <internals@lists.php.net>; Thu, 01 Jan 2015 09:19:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type;
        bh=EMkz0Jo8A9rq9cz2/rXofz1vkPnDOkC5716j42hr1Kw=;
        b=QrqrgfO3PsYpbXygzmu/K25+KKPHbWL09f39mbr1pVKdC9QglUTR0H2xoLvEAbPLET
         orLpm5WQLeDatGL4rEBlR9wwJHjzlr0+S08tmbrxS2Ta9ocsf7nK7hqFrkZuFCUENogT
         t2N9h8clY4eULkuqtEbbB8H9/Yd/uLRWiuM9U0J/ObDKBTV5jNfpQq/b1Bdg78LlK0M7
         bNYStRDeie6St4I/KTgeUUssYU+UM9Lrbz+IaIjwr80Y8UyGXFBqbkBadwNtTIgqlY2U
         ID2C8dUFETNfQ5puk5nPHD2M1DD+QtnbtnhVVXwJS2DsdnQG5bY2mwj1sBDTZmRD6mn1
         tqmw==
MIME-Version: 1.0
X-Received: by 10.202.182.11 with SMTP id g11mr39267716oif.13.1420132791003;
 Thu, 01 Jan 2015 09:19:51 -0800 (PST)
Sender: morrison.levi@gmail.com
Received: by 10.76.89.237 with HTTP; Thu, 1 Jan 2015 09:19:50 -0800 (PST)
In-Reply-To: <20150101164402.EB1442605AB@dd15934.kasserver.com>
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me>
	<CAF+90c-uiLj1QoT+dXfd1obRXNcYcpBAJ-aU59yEXk+HYNZRFw@mail.gmail.com>
	<20150101164402.EB1442605AB@dd15934.kasserver.com>
Date: Thu, 1 Jan 2015 10:19:50 -0700
X-Google-Sender-Auth: cuoki6vrOD7OVCkJuPxlLEty-D8
Message-ID: <CAFMT4Nq0cD_YDMGDGdT4nev+k5KYMJhZzKOh8_UHAcRbt5JPhA@mail.gmail.com>
To: Thomas Bley <mails@thomasbley.de>
Cc: Andrew Faulds <ajf@ajf.me>, Nikita Popov <nikita.ppv@gmail.com>, 
	internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: levim@php.net (Levi Morrison)

On Thu, Jan 1, 2015 at 9:44 AM, Thomas Bley <mails@thomasbley.de> wrote:
> I think it is no problem to add strict parameter type hints with another rfc (if this rfc gets accepted), e.g. function foobar(string! $str, int! $str){} or any other syntax.
>

I would rather have it the other way around. `string $str` is strict
and some other syntax (notably `(string) $str` or `@string $str`) can
be loose.