Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:124511 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 55D231A00B7 for ; Sat, 20 Jul 2024 14:30:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1721485919; bh=aEENAFVE5C+7yHi3NEfVqH2aV3hlayjH+Qjy0+b238o=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=LqJa4CDYLrwpr45mY2dGAdLvXWj0vPo52Z3F79F6hkqItjKb8NtIxXV17knrMccRl WrgKQzTSRNPOLecHetryxF6je/QyPyYvjyhep7V1VpCkc37E9IpQ8kzsh9omHO3cyg MVdUn4g1LfgGrPFP2T7rErQ+/Mbh7ex1EMNNyaSwIt+x5uWe158o85PbbDhrnn5baC 82Zv857kiEgUqTySFlBroujWsfW9mJUISraWaabkzLg3GdYbA6V7ZdGYS1x8y8nTRQ mlFirJdGtwihk+OGFDQqI740fSNYBWQ38ZkFxilVhBAjmZzFJIPNj1Vdg1i8Ti3Sm1 h+jXnQKEhZ4VA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 33459180052 for ; Sat, 20 Jul 2024 14:31:59 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 20 Jul 2024 14:31:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1721485824; bh=PTkdaXBmVHijGOJd2os6SE3zYjP/V+89xOIoZxKrKr4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=f9TUW7vi5PXTR0bz33CdaJ8o3evZgSFDxCmnDf1pTBTqr4YRvUJzi1CrU1pF7Omra aLkm/2IpbM2VimORDybLJeLNhbA1vG6FgRgoml68DgSMYdc+jAJt3Ji0tZOGNBgh+X J92nCJ6V8Vpp0FNN4e1kWqbso163J+SZIuIqwB6kA96eyHmi80og6hbSizuOxpMCYA EZMhRIHzYPFgbBRXs5xe+xH9kx6tnsjSQlS0WS67qKysttuovZbtyGu8FAl2g+IYtw yDUMujEWBsLBwGKKrRA91tpW7NKZZsHxBO4eb7iKwYq1kOFEKnUmPg+y3ClnmZv1x4 6U+risCL1CK8w== Message-ID: <237f2004-92dd-46e5-9946-91b8c8d97166@bastelstu.be> Date: Sat, 20 Jul 2024 16:30:22 +0200 Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Subject: Re: [PHP-DEV] Request for opinions: bug vs feature - change intokenization of yield from To: "Christoph M. Becker" , =?UTF-8?Q?Marco_Aur=C3=A9lio_Deleu?= , Juliette Reinders Folmer Cc: PHP internals References: <66984FD0.5090805@adviesenzo.nl> <84999002-cff1-436a-8036-b7b4facb2cba@gmx.de> Content-Language: en-US In-Reply-To: <84999002-cff1-436a-8036-b7b4facb2cba@gmx.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi On 7/19/24 00:51, Christoph M. Becker wrote: > And frankly, how much code would be affected? I mean, does anybody > actually put a comment between `yield` and `from`? Is there a case > where this may make sense? "Because we can" isn't a strong argument, in > my opinion. I don't really follow this line of argumentation: If folks do not use the syntax anyways, then we do not need to have this discussion, because the tools can just ignore it existing. That also means we do not need to revert the change in PHP. If folks use the syntax, then reverting the change is a breaking change for them. So either the revert is not doing anything at all, or the revert is actively harmful. I do not see a situation where reverting the change is a value-add. Best regards Tim Düsterhus