Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121022
MIME-Version: 1.0
Date: Sat, 9 Sep 2023 00:16:07 +0200
Message-ID: <CAPyj-LB16MUDNkgdQ7TrHpgNG2gD86H7+OP_g_rbuH0KYR9ZzQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: [RFC][Draft] Match block
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hello everyone

I've been working on match blocks over the last few weeks.
https://wiki.php.net/rfc/match_blocks

I've already shared it in R11 and got conflicting feedback, which
makes me unsure on how to proceed. We have a few options.

1. Add blocks only to match, possibly adding blocks to other
constructs in separate RFCs (the approach of this RFC)
2. Support block expressions as a language-level concept, analogous to
https://doc.rust-lang.org/reference/expressions/block-expr.html
3. Do nothing

The two main complaints/questions I've gotten was whether this
approach is the right one, and whether the syntax can be improved. The
RFC tries to go into detail on explaining the rationale for the chosen
approach. Additionally, it proposes a few alternate syntax options,
although none of them are very satisfactory.

At this point I'm unsure whether a proposal can satisfy all camps. Let
me know if you have any thoughts/ideas.

Ilija