Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121435 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 97990 invoked from network); 19 Oct 2023 17:52:01 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Oct 2023 17:52:01 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7AA47180546 for ; Thu, 19 Oct 2023 10:52:00 -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,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE 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-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 19 Oct 2023 10:52:00 -0700 (PDT) Received: by mail-pf1-f181.google.com with SMTP id d2e1a72fcca58-6b6f4c118b7so15876b3a.0 for ; Thu, 19 Oct 2023 10:52:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697737919; x=1698342719; darn=lists.php.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sUtIrfddp/rywPtt2fB2Nu6XpB4YRGL7v7KT4t71/zo=; b=T4MmTz+POQIZlZ3ztn/EwRlX2dWfktCj0UWVo3N32Xmu8N+e9d9NTp6pqMAWo2I9MK SlS4+n9tUmHB3/gw3KNv379LIcivpHxsIzHxxdFUQeC+vSss4XllEGcnDvmqUWdnRgVq pjs8MnETi9Ad7kokrLE0Sdb+C4xaG3B5bc3hR+uDDGs4zxrTOx4b+YGE9zgdqzZV4Bhy FR4MBicMCqy8jVusbCSmDYJmbtYRlYrfw1Y36ETsZZXt8gpV8l44nxi0FcxF3zdg0zSQ fwhBOaf++qf6vpyUPr19CalbN3kO2JDQGy4Tz5vQJ2AAEwQwoK2AOmf9+Uy9/n8yjhx2 wlsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697737919; x=1698342719; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sUtIrfddp/rywPtt2fB2Nu6XpB4YRGL7v7KT4t71/zo=; b=jAdllwFBwuncfsYGkU1aH1+e1rxwPK8A6z3WivDL01Ec9FK2j2UodYfdSLy6Ddx2EQ HfJOY/J1habvabbfjhbZJ3DtkAj5p9twCxuVjuYFXxcAyh4a0mDPRQs8joWpoijeuj9X S+gRLTAdmgO35dQA9sTIPkC+c1ixL1lVWSX3h1iHA6/ZfdbaKeHlOj8hImAiU/v3UjPy M15tbg6P7uYUmTebV0hOEDaMimxLpWeJTA/EB6t0MX9C3BNbhZXRBGyxlJJxBIMUWegk 7SqyvUTzfKCaI1lRaRS/doLOrpD97ql/9splwDCnyg9GtrneF7RFJkA7Ghl0Rp3CdyYw izuw== X-Gm-Message-State: AOJu0Yxk/kC1oluZK9s43A3KKjGuuKBt5vDs+b+2KZtsMQcAmqYa6UAF DOxvhK39Zi0z+DycfVcDFs13wxtwnRyKuQ6oYjU= X-Google-Smtp-Source: AGHT+IHOGAPNOc2hsxbyLqEpyzs24ejy0jGn8FCGLBwyxzGp6bJuCu6PwMSAEZHrNBFYaDbC5ateKbxRn348Jzf/uo0= X-Received: by 2002:a05:6a21:181:b0:159:b7ba:74bd with SMTP id le1-20020a056a21018100b00159b7ba74bdmr3776068pzb.50.1697737918779; Thu, 19 Oct 2023 10:51:58 -0700 (PDT) MIME-Version: 1.0 References: <712f1499-77cd-4897-bc8b-e13468d5c598@processus.org> In-Reply-To: <712f1499-77cd-4897-bc8b-e13468d5c598@processus.org> Date: Thu, 19 Oct 2023 10:51:45 -0700 Message-ID: To: Pierre Cc: someniatko , php internals Content-Type: multipart/alternative; boundary="0000000000009218d2060815698f" Subject: Re: [PHP-DEV] Custom object equality From: jordan.ledoux@gmail.com (Jordan LeDoux) --0000000000009218d2060815698f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Oct 19, 2023 at 12:14=E2=80=AFAM Pierre = wrote: > > Maybe I don't master english enough and I can speak to strictly > sometime. If an operator overload RFC that doesn't have any blind spot > or weird edge case happens, I'd be happy to see it pass, at least it > would close bike shedding around this topic and life would continue > happily. > > I can't vote, but if I could, I wouldn't vote against a proper, robust, > and easy to debug for developers operator overload RFC, I would simply > abstain, because even if I personally don't like it, lots of people want > it and I'm simply one among millions of PHP users, I don't want anyone > to be frustrated. > > The most important thing in my previous message I wanted to say was that > the "~" symbol refers to something "approximate" in many contexts, in my > opinion it's not the right choice for an equality operator. My opinion > is either go for a full-on proper operator overload or simply don't. > > Regards, > > -- > > Pierre > > I tried to make sure this was clear, but I will say it explicitly just to make sure: I am not at all criticizing you, I was just saying that the opinion you expressed is one that is shared by many voters so it cannot be simply dismissed, and that I disagree with it personally. Jordan --0000000000009218d2060815698f--