Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:125568 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 D96DE1A00BD for ; Mon, 16 Sep 2024 16:36:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1726504720; bh=JeOQyXOpAuW7pKM9Xv8F39WDO8tRo7sjq0ucwiupXcM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=HVjeI//qLilcQ79a8cJYfhtdgIgTxTMiw165rGuSbevFXtt49ien0r0Q6LdNOpxYq JRJcqx8D5eN03xsg1PofPLA+gfLQ51SH/cLQpmD6TmbP2TgvC5zjCZNjJKY7wisAXv vxXjrV89LdV90CiroTqvcwpiaZsOQ1LdSfxsCrx468iBOxcoK+JxMHIBAvWYJXfzgf +9pMO2D4qB2Lqqd2QJ1vyxykwx89usQowBGOQhs6LJfM+FN/fRa143qzys/fbTGTDg ASq3IT2FwDPbTKArCafGa3IaTCPJ6PrtQX4ePAzpxThZIPB4Q3WsXzQP1Cl/cq8135 nDjEw/QvHr6fw== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BFF76180042 for ; Mon, 16 Sep 2024 16:38:39 +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=3.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_PASS, SPF_SOFTFAIL autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from xdebug.org (xdebug.org [82.113.146.227]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 16 Sep 2024 16:38:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1726504594; bh=JeOQyXOpAuW7pKM9Xv8F39WDO8tRo7sjq0ucwiupXcM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=lPAEmggqLNNtngAWYw08LNR5vJx4rp4CtWS6J+dAz2FOwH5WHheJdMcERAqyN+4Jx drvAM1KURTDMg3ktCQBJxbZPc+fgMhqEF2jgOk6RQkn/De9H0xornUMKstQogh1veA vpTSLOae7W69yC237OYAYgKfcHhmREimghua+J8qxX1LCj0ixKJFWAmAG/YldhU8OG UTQMDKmgZ6juz77El/IFN9tsig/zUVX86LzHY8v0mIWzIpHxnVAQdCg+oe6sKdbUxs RilO7X7DQvwAxK8nI/E4UX1wvOUv8TA9e33Y3IYstvOUD1gylOwAqtpfpDhqEJmITL dS2Og4F6fSYZw== Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 3862010C036; Mon, 16 Sep 2024 17:36:34 +0100 (BST) Date: Mon, 16 Sep 2024 17:36:34 +0100 (BST) To: Jordan LeDoux cc: PHP internals Subject: Re: [PHP-DEV] [Pre-RFC Discussion] User Defined Operator Overloads (again) In-Reply-To: Message-ID: <844060c9-a0d7-d8e2-40fa-bbd906b6a060@php.net> References: Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII From: derick@php.net (Derick Rethans) On Sat, 14 Sep 2024, Jordan LeDoux wrote: > I want to discuss what changes to the previous proposal people would > be seeking, and why. The most contentious design choice of the > previous proposal was undoubtedly the `operator` keyword and the > decision to make operator overload implementations distinct from > normal magic methods. For some of the voters who voted yes on the > previous RFC, this was a "killer feature" of the proposal, while for > some of the voters who voted no it was the primary reason they were > against the feature. I am still generally in favour, just like I was on the previous iteration. And yes, I would say having the "operator" keyword was a "killer feature" for me. > I hope to start off this discussion productively and work towards > improving the previous proposal into something that voters are willing > to pass. To do that, I think these are the things that need to be > discussed in this thread: > > 1. Should the next version of this RFC use the `operator` keyword, or > should that approach be abandoned for something more familiar? Why do > you feel that way? Yes. Making it clear what happens is useful. > 2. Should the capability to overload comparison operators be provided > in the same RFC, or would it be better to separate that into its own > RFC? Why do you feel that way? I'm not too worried, but usually smaller RFCs have a larger chance of being accepted. cheers, Derick