Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111378
MIME-Version: 1.0
References: <DM6PR07MB6618916B074C7C1467DB1A9BF9460@DM6PR07MB6618.namprd07.prod.outlook.com>
In-Reply-To: <DM6PR07MB6618916B074C7C1467DB1A9BF9460@DM6PR07MB6618.namprd07.prod.outlook.com>
Date: Sat, 8 Aug 2020 18:09:33 +0200
Message-ID: <CAC5V6ghPVvi3K+ONybke_2E1yw7niBaWVkSEGsBhYaCAX5Fv+g@mail.gmail.com>
To: tyson andre <tysonandre775@hotmail.com>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002d890d05ac5ff3df"
Subject: Re: [PHP-DEV] Putting the match expression in constant expressions in
 PHP 8.0 or 8.1
From: guilliam.xavier@gmail.com (Guilliam Xavier)

--0000000000002d890d05ac5ff3df
Content-Type: text/plain; charset="UTF-8"

On Sat, Aug 8, 2020 at 2:22 AM tyson andre <tysonandre775@hotmail.com>
wrote:

> Hi internals,
>
> The match expression can be thought of as a much more concise/readable
> equivalent to chained ternary operators.
> I'm proposing allowing matches in constant expressions when all parts of
> the match are constant expressions.
>
> For example, these two class constants would have equivalent behaviors if
> match expressions were allowed in constant expressions.
>
> ```
> class MyClass {
>     const CONFIG_SETTING = (APP_ENVIRONMENT == 'dev' || APP_ENVIRONMENT ==
> 'stage') ? 'development-config' :
>         (APP_ENVIRONMENT == 'prod' ? 'production-config' : null);
>
>     const CONFIG_SETTING = match(APP_ENVIRONMENT) {
>         'dev', 'stage' => 'development-config',
>         'prod' => 'production-config',
>         default => null,
>     };
> }
> ```
>
> https://github.com/php/php-src/pull/5951 implements the main part of the
> change.
>

Hi, thanks, just noticed that your examples should use `===` not `==`.
Regards

-- 
Guilliam Xavier

--0000000000002d890d05ac5ff3df--