Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110602
MIME-Version: 1.0
References: <CAPyj-LB7jSiv+7DheaYpEcZXbjeJ9OMsRUTMOofnWbH4LyOQhA@mail.gmail.com>
 <CAPyj-LCV640AZpc=GPb2A+FxqWcSgnzzAH0VVLedCuM0RawmVQ@mail.gmail.com> <37f1f8fb-0e1b-cc39-f4b6-6c943a731d49@telia.com>
In-Reply-To: <37f1f8fb-0e1b-cc39-f4b6-6c943a731d49@telia.com>
Date: Tue, 16 Jun 2020 18:17:00 +0200
Message-ID: <CAPyj-LAreEydWbK1JcBduQuDtu8r4Bv5a-Oma7mFkr3H2Y3y2A@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [RFC][DISCUSSION] Match expression v2
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi Bj=C3=B6rn

>>> I'd like to announce the match expression v2 RFC:
>>> https://wiki.php.net/rfc/match_expression_v2
>
> I do like this RFC and have one comment. Would it be suitable
> to have : as a separator instead of =3D>?

`=3D>` is usually used in combination expressions (arrays, yield, arrow
functions). `:` is mostly used for switch cases and the alternative
control structure syntax [1]. `=3D>` also visually separates the
condition and expression better IMO. This has been suggested once
before but that's not enough for me to change it at this point.

> When reading the Future scope of the RFC I noted that arrow
> functions was part of that, so are we here overloading the usage
> of the '=3D>' symbol?

The future scope mentions possible block support for arrow functions
in the future (`fn() =3D> {}`) but we use arrows or colons in match
doesn't matter.

Thanks for your feedback! :)

Ilija

[1] https://www.php.net/manual/en/control-structures.alternative-syntax.php