Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109295
User-Agent: Microsoft-MacOutlook/16.35.20030802
Date: Wed, 25 Mar 2020 16:29:13 +0100
To: Larry Garfield <larry@garfieldtech.com>,
	php internals <internals@lists.php.net>
Message-ID: <2E98378A-605D-40ED-898C-6ABBFBD091B9@me.com>
Thread-Topic: [PHP-DEV] [RFC] switch expression
References: <047092C7-84FB-42AB-8084-7B83F76F55C1@me.com>
 <CABdc3WrX2M565H6af7axCgy=Kavairac8iVN4EkgtVCbu0H1mA@mail.gmail.com>
 <4513B88E-CA5B-4DF2-94C8-242BEE54ADCC@me.com>
 <767910ef-d27b-404c-9ad1-037105c69d12@www.fastmail.com>
In-Reply-To: <767910ef-d27b-404c-9ad1-037105c69d12@www.fastmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] switch expression
From: ilija.tovilo@me.com (Ilija Tovilo)

Thanks for your feedback, Larry!

> One possible improvement to either version is allowing an expression on the left side.  That is, rather than doing an equality match, do a boolean match.

This is how Rust does it:

```rust
let x = match ... {
    Some(y) if y < 5 => ...
}
```

In other words, you can add an additional guard to each case that excepts any expression. We don't really benefit a lot from that since we don't have pattern matching. I don't think this would add any significant benefit over:

```php
$x = true switch {
    $x  !== null && $x < 5 => ...
}
```

Regards