Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116807 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 28763 invoked from network); 5 Jan 2022 01:25:17 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Jan 2022 01:25:17 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3818D1804A7 for ; Tue, 4 Jan 2022 18:32:38 -0800 (PST) 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,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (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, 4 Jan 2022 18:32:37 -0800 (PST) Received: by mail-ot1-f51.google.com with SMTP id v22-20020a9d4e96000000b005799790cf0bso49475112otk.5 for ; Tue, 04 Jan 2022 18:32:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gu4eZzuRbwuVTkMTQgyvSb53Crp35ho/vvQYcnvM6fE=; b=fiuD8KlpR9EllmiLK/PjwRrXba5t+2PGd8s3L0JDCkssZbB635ggTEF0eLhRwCg2eH 1AvcTgXkhfIjSSRug3IPNFjsWKHjA7tob41dtq9c2g+CiZQVeiFfIOCsFKqbXGUbxln5 lenfd4v2my8bo8WMnAVN1xlr3qJfEYh5hY6W72PVhXdrvUGV6kjZ/n4Ys+5k9Nogv5de bCZv9WsW10PnPxzmLUCi7dPn6AO/K3M+qP8RU8iVokfDYQkT72TG7xQU6UsTEAm6DFAJ g6A4XkFAqYBTPX7jPmdIewX+2zLwzfQaCtSzEhBGoX63tSY1PASZopcQm3wLQ6zsypYJ 7aeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gu4eZzuRbwuVTkMTQgyvSb53Crp35ho/vvQYcnvM6fE=; b=KmhiW5mcP0j455a6QLFFcO5EzL3L3xHKYEwJS1WBX/9yauPuqPxOV/k3vssn5ZmeUm IobdbbFKq0GW80JkAA5weN7f6YyzGzW5QYjZKuDBusC0qYXH6zTRbugNq7fFvEcoCwRp 3G0U+RMirHF1eI2jdO+K8cKgnnt78jUqzNLZE5Sqh/qeewpMLocBWTnikiGjgVeZMVPf Jcgo0jtFtflAreKUR7a6Nyur2WNQCNsMrh0M96HClYvKxjQ3BwCle8ELYmh4RvPvh2i+ ae6KJXDJlRmIX+3EMcrFhJWNKoUK8iZqhRqIWX7zOOtmvZqKqSqV7n3K7IpnpzPahOYG cpyA== X-Gm-Message-State: AOAM5300myeLNTOi+7fc/FAbfNlDtYjndYRjZNrbottlXZcOoaU9A1tH Q/HEhO2S40A0LEhc/jlYapYCn/r05P2V8q26zdM= X-Google-Smtp-Source: ABdhPJz8Pe4rnqT4ahCE731QhEpd431Ee1KsrShS+zu3Q7RheqXNqVUVmY3yLkZceRG4r8EBBrLScl5A2UitCaGdUwI= X-Received: by 2002:a9d:1b41:: with SMTP id l59mr38448498otl.318.1641349956696; Tue, 04 Jan 2022 18:32:36 -0800 (PST) MIME-Version: 1.0 References: <3225c921-9b26-d2e0-f76f-45fff6f5a12a@processus.org> <40a1e5fa-396d-d9ef-93ab-6fcfb5054092@processus.org> In-Reply-To: Date: Wed, 5 Jan 2022 03:32:25 +0100 Message-ID: To: Jordan LeDoux Cc: Andreas Hennings , Pierre , Larry Garfield , php internals Content-Type: multipart/alternative; boundary="0000000000001f060405d4cc918e" Subject: Re: [PHP-DEV] [VOTE] User Defined Operator Overloads From: ocramius@gmail.com (Marco Pivetta) --0000000000001f060405d4cc918e Content-Type: text/plain; charset="UTF-8" On Wed, Jan 5, 2022 at 3:19 AM Jordan LeDoux wrote: > > On Tue, Jan 4, 2022 at 1:27 AM Marco Pivetta wrote: > > Can I expect this for other math related RFCs, or is this dogmatic about > operator overload specifically? I have no clue, and at the very least, I > would like to learn that. > It's in the name: "overload" You can certainly expect pushback from my end for any implementation thereof. As I mentioned above, your RFC is well implemented: I oppose the feature, not the implementation. Greets, Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ --0000000000001f060405d4cc918e--