Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110704 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12597 invoked from network); 23 Jun 2020 09:47:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Jun 2020 09:47:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 24ED11804C3 for ; Tue, 23 Jun 2020 01:34:18 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 23 Jun 2020 01:34:17 -0700 (PDT) Received: by mail-yb1-f176.google.com with SMTP id y13so10484695ybj.10 for ; Tue, 23 Jun 2020 01:34:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=KkpH6K9ECdKDbTCY62oNQs5nom6VQHx03sNmAMjqouo=; b=DObJYVKOLQ2XUnQyBHsMnGsNbP34ZNjePdQXO7qs9FjEIgIljAfV3F2vbyqvhZk++K PKlLxs8Yb2KftWnG85/Mgo7Q6vYoN+QmEp9OTP3BOkBx/bxXhR6wsvu4S7bCPGicxY9q YG91KaDeoa9C4+Vnln9kwy6PzRUlX4lmSR/L7t/YblG9ztfPe89KGhInEzUn6RS14Z0/ mCDdjpUh9C17/df1oFqH4rqj8MwBsA7FZb9rEWlsmO6jVSDbfnZWZSFaMay0IbgYfq+P u5e6a0H5GvEpSVIkCrPqkkB9v+2dgyRElDJXEjhN11YKwwsiSIqZXuBMHA5URfXn1deM gALg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=KkpH6K9ECdKDbTCY62oNQs5nom6VQHx03sNmAMjqouo=; b=ZI4aW7XYfEdiJH3XdNhKjy3N8BEAz4NdcG8zku4IMnbPqbzt6bxxSsokmGn4vyi7aY OplF32eWBdT2PeV9resUL3raY3uDSiKVkyZUavuF0C05lyCMJuukhs+ZRuCMQ+3Fhmol DqurwNF2Lc76GSZdYVUeKcYHHfqnrGlb5FKOXt2ysFfzgu2+WCVDTH9rLbDtahY8/Snq xupIHxucyi/HYQ9yQheglS0vJqxGAb3EXm7NWeIezWnT14pBtclCZLYipXWZSRa5Dc7V GKYou4C/0fH0mUiWUxyICmN/2LPWLbSW8kdzBEVAtUMx7g7d4bIPQezKtVXE/iVpPcub BAUw== X-Gm-Message-State: AOAM532hVZ6JDNF3gvLII9bXNMuJQTj+mj2M3RM1Vm3rEszs3mdcvw+0 1ufJ+CSaz5MAAIxkyApUCmClsab6xDwMjZHc1rg3kcFX X-Google-Smtp-Source: ABdhPJxuFhFhlAgUmPhvJuBazH9bhy5ukTpp/9F2x9qSHebgp51oaGc5Cn5Hwb5lYLRrNaPQCkyZVSMOHQTFZaPi5ew= X-Received: by 2002:a25:20c4:: with SMTP id g187mr34617430ybg.347.1592901256224; Tue, 23 Jun 2020 01:34:16 -0700 (PDT) MIME-Version: 1.0 References: <37f1f8fb-0e1b-cc39-f4b6-6c943a731d49@telia.com> <250b7671-2919-9385-c149-931212397e4b@telia.com> <04d86e2d-0815-195a-6111-3034e0ca5918@telia.com> In-Reply-To: Date: Tue, 23 Jun 2020 10:34:05 +0200 Message-ID: To: PHP internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Re: [RFC][DISCUSSION] Match expression v2 From: tovilo.ilija@gmail.com (Ilija Tovilo) Hi Benas >> I'd like to announce the match expression v2 RFC: >> https://wiki.php.net/rfc/match_expression_v2 > Then it's not a standalone expression but a block. In this case, you cannot add an optional semicolon at all. > > But this RFC v2 is not proposing to add a block, therefore you won't be allowed to use `match` construct as a standalone expression anyways. Using match as a standalone expression is definitely allowed, just like any other expression. // This is fine, the semicolon is required match ($foo) { $bar => baz(), }; Ilija