Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111371
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 02:35:50 +0200
Message-ID: <CAP=4hC+x5LY=gp6=wywp_b7e2XnbZT4bazpDK5_aV60TLhY5JQ@mail.gmail.com>
To: tyson andre <tysonandre775@hotmail.com>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000031e07b05ac52e8b0"
Subject: Re: [PHP-DEV] Putting the match expression in constant expressions in
 PHP 8.0 or 8.1
From: carusogabriel34@gmail.com (Gabriel Caruso)

--00000000000031e07b05ac52e8b0
Content-Type: text/plain; charset="UTF-8"

On Sat, 8 Aug 2020 at 02:22, 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.
>
> This is mostly for the sake of consistency, since match can be thought of
> as yet another control flow primitive that is more readable under some
> circumstances.
>
> So I had some questions:
> 1. Should this target 8.0 or 8.1? I'm leaning towards 8.1 since the beta
> is already out.
>

8.1, as PHP 8.0 is already FF and I'd consider your proposal a feature,
we'd need an RFC and everything else :)


> 2. Are there objections to doing this?
> 3. Should/shouldn't php enforce that the default arm exists for match *in
> constant expressions*
>    (constant expressions can already throw errors when evaluated for
> various reasons, but UnhandledMatchError is new)
>
> Thanks,
> - Tyson
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--00000000000031e07b05ac52e8b0--