Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128068 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 lists.php.net (Postfix) with ESMTPS id 988201A00BC for ; Tue, 15 Jul 2025 20:23:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1752610883; bh=Oj4UbexP7ukOpuM+dhXqDHjwKaaBbUWaONVrzxbDovM=; h=Date:Subject:To:References:From:In-Reply-To:From; b=Oobs+nlZ6Jsp3ic77ulb2TdP8rgsgtmAd72Jccrl+QCRi/ImxchzArInHSTYxLDUx +sWVdCghOKSEEfKMTHC2m5fr7egWfmvFaPruJOtwYrkM4TANRurlNXLe+Drm51XLbl B9IORUM6DnbRKLafJtqkwD0VavQ/NRLH9foXW3YBqT+j96KedW0P5pQCYWdP4jsohT sToqkREqLnFj2ZapgQEmhMGG8dpbUbaPJ89Ocyj0IqHSK/zYHba2v/EoTM0G4ZTMJD 55SK2Fy4S0Kukz9vRUvebFmtZ/zUagCm0kai3IFfrbTwSCEOOxy9e6WA2KG5sAKQ5s /A2025J1YkZAg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6063518006A for ; Tue, 15 Jul 2025 20:21:22 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) 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,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) 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 ; Tue, 15 Jul 2025 20:21:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1752610988; bh=nP1oFbOO8rHUsueqwjGgzvPbpERVL3dAyQ0aESWNG4Y=; h=Message-ID:Date:MIME-Version:Subject:To:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=butD7eLK3fucet9sGzl2lW93y2lXMdJbko6IsplXKJq5B6ZckQIv6K2cx00/dGAxF MqGyzdWKixEGR8F3A9Dq3bRi5XwlG6It9afM9i3JmzaKeBLz7dK683kLtCKwBdJoj4 auty+RD+D4ez7uGpcUGRmv7LkKKL2RDzi3JUAE42FAvbGRV/EDJqP3Hpsj1BMk3c7+ ap3uBhqC/5Ghr/YBoS7aaKds/DSP4Y+M0xL29+oyys1aDZQtA7zXzHarKIufyiyo/r rDkx7MfPmhLUfYMUnm9tuXuQ6+zzgFub0lVpBKL1Ptsgxn7gtQe74XpV1Nza7rJU09 kZzMPFOQgwhCw== Message-ID: <3cbe99a8-3415-45d3-aaf5-b5f921aab5e5@bastelstu.be> Date: Tue, 15 Jul 2025 22:23:06 +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] [VOTE] Single-Expression Functions To: Dmitry Derepko , PHP internals References: Content-Language: en-US In-Reply-To: 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/15/25 19:56, Dmitry Derepko wrote: > RFC: https://wiki.php.net/rfc/single-expression-functions > Discussion: https://externals.io/message/127423 > PR: https://github.com/php/php-src/pull/17677 Thank you for the RFC. It probably does not come entirely unexpected that I voted against, given the feedback I provided during the discussion in: https://externals.io/message/127423#127577 I'd like to note that the start of the vote was very surprising to me. As you acknowledged yourself, my email regarding open questions and issues with the RFC has been left unanswered for more the a month and then you started voting 15 minutes after your response and making relevant changes to the RFC. This short of a time did not allow me (or other readers) to carefully consider the latest changes, which is the point of the discussion period. In fact the $a = function() => 123; example that I mentioned in my email and that your response said wouldn't be allowed as part of the RFC still is in the existing proof-of-concept implementation. The RFC text itself also doesn't clearly specify what changes are proposed and instead just uses some handwavy language "This RFC introduces a shorthand syntax for functions that consist of a single return statement". In other words: It's not clear to me what changes to the language would happen, were this RFC accepted, since the RFC doesn't clearly specify it. The implementation is not the source of truth (and contradicts your response anways), unless explicitly specified in the RFC together with a clearly specified revision. Best regards Tim Düsterhus