Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100511
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.174 as permitted sender)
To: "internals@lists.php.net" <internals@lists.php.net>
References: <eb28362c-4f8f-45df-bbf0-582e8ad2b8af@Spark>
 <DM3PR18MB07647618E0682A20C05C255FDE6B0@DM3PR18MB0764.namprd18.prod.outlook.com>
 <CANUQDCg-gUUpvpgq-PR4xzf9spMiS+AH+L8FhN9gBkcrohQryw@mail.gmail.com>
 <508bb95c-162f-b1c0-f76f-08aa9bf2e93e@gmail.com>
 <DM3PR18MB07645D39FC3D93B73935FC9CDE6B0@DM3PR18MB0764.namprd18.prod.outlook.com>
Message-ID: <218d59c9-c3dc-3ae4-2eab-5cd36e76c8cf@gmail.com>
Date: Sun, 10 Sep 2017 21:18:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <DM3PR18MB07645D39FC3D93B73935FC9CDE6B0@DM3PR18MB0764.namprd18.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Match expression
From: rowan.collins@gmail.com (Rowan Collins)

On 10/09/2017 20:16, Theodore Brown wrote:
> On Sunday, September 10, 2017 12:45 PM Rowan Collins 
> <rowan.collins@gmail.com> wrote:
>
> >>> Would it be possible to add an optional `$strict` parameter to
> >>> switch? E.g.
> >>> ```
> >>> switch ($i, true) {
> >>
> >> I'd very much prefer a "strict switch ($i) { ... }" over a second 
> parameter.
> >
> > What do either of you think of my "switch-use" proposal, which would 
> spell this as "switch ($i) use (===)"?
>
> That seems more complicated and confusing than either of the other 
> options. Normally `use()` is for inheriting variables in anonymous 
> functions.


The choice of "use" as the keyword was largely because it's already a 
reserved word, with multiple meanings in different contexts. As well as 
anonymous functions, it's the keyword for importing names from other 
namespaces, and for including a trait into a class. I would be perfectly 
happy to hear alternative keyword or syntax suggestions.


It might not need a keyword at all, as it could just be "switch ($i ===) 
{ ... }" or "switch ($i) === { ... }", although I'm not that keen on 
either of those.


However, I think using "===" in some form is definitely clearer than ", 
true", which could mean anything; and even "strict" could have multiple 
meanings - for instance, a "strict switch" might be one where "break" 
was mandatory.


Regards,

-- 
Rowan Collins
[IMSoP]