Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119386 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 29053 invoked from network); 20 Jan 2023 19:44:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jan 2023 19:44:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 676C41804B4 for ; Fri, 20 Jan 2023 11:44:08 -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,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-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) (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 ; Fri, 20 Jan 2023 11:44:04 -0800 (PST) Received: by mail-pf1-f170.google.com with SMTP id w2so4736803pfc.11 for ; Fri, 20 Jan 2023 11:44:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=bvFM9oZrm941SRZBnuCR88Ajra9bZGV8z8NZKWZKKtk=; b=YllAunM3GydkfgD8bcVvr9t5pXxYdbfdJf5qX7RMMbN40zVyzA+sifLUIsqbnchicZ F51WTiE7I4ZuSB2JpwKsyqdZmOFYhCTAZY5IUL3ha0F0l0OX7BKOqufsbZdwwS/4KwiB CrQdSxPJEtbHmbbnEW8fdbqPjP2KnwiNemPyagXu01xcfu+09h90BMNAUIT6iGKFi/C3 ktmzcR/X0cmTOzyHeYH/XYlbNWKoqlpiXMIj3x1RR6zsxUV+JeO2p0w4CVHU7V4qzvLN Nc6POrPs/Zn5rLhyDyJ3ll5Feyu0LdRLEJ3T6qIeYFnGHoL++a6ABIlRzYzygPziV+Dz SdHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=bvFM9oZrm941SRZBnuCR88Ajra9bZGV8z8NZKWZKKtk=; b=EEW77YxHyDxzpzTZBQB5g39FTXVViF6ykIe1Y6UbS8HhWWfpoOmGbVEzNsu4VnlPm8 BCUYe66wGCDMO+ipTsaXVXpTMV2ypl9ZFOtK1CEW1rSH7YCX1LlIOD5/6FKTiVpBxKOc IxM66WK9h5T8nadIXthw1sS9Y5Y2ZC54YjosftOeVOQ8Mot00OfKduyFkCqxqTZAIhBk TS2QkOOSvJAnQ/ZupieTdmHOYuDcFLITp5ElyEF4PsMxGEhvivm/pvJOG4RUdbCYdVY2 QVIeuRT/5aa69zUYJdLBZ+zr2Ue70+bnBXtzqI65yARCp0OBhMVntHF+MooHKssCRQ3N CVWw== X-Gm-Message-State: AFqh2krXVxqlmHFbky56HHEutRilc6yA8itH7mX4SIwHRTGkOuVPzAGD GHeCKbtc14vYp9jpbElqVc0q199AaFomHe2gEJm9kQL4 X-Google-Smtp-Source: AMrXdXttOUxVO6iHSCAvpaUKtHrgieeFlZ6yGJsvo5+r4HJN1yLUvx4z/lN2Z/oiErI4TI+Ikga/hn0OeicMB1od76Q= X-Received: by 2002:a65:6a53:0:b0:476:d785:71 with SMTP id o19-20020a656a53000000b00476d7850071mr1718023pgu.161.1674243843640; Fri, 20 Jan 2023 11:44:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 20 Jan 2023 11:44:28 -0800 Message-ID: To: "G. P. B." Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000091550905f2b7451b" Subject: Re: [PHP-DEV] [RFC] Path to Saner Increment/Decrement operators From: jordan.ledoux@gmail.com (Jordan LeDoux) --00000000000091550905f2b7451b Content-Type: text/plain; charset="UTF-8" On Tue, Jan 17, 2023 at 6:28 AM G. P. B. wrote: > Hello Internals, > > I would like to start the discussion on the Path to Saner > Increment/Decrement operators RFC: > https://wiki.php.net/rfc/saner-inc-dec-operators > > The goal of this RFC is to reduce language complexity by making $v++ behave > like $v += 1 and $v-- behave like $v -= 1; > > I am expecting the contentious part of the proposal to be the deprecation > of the PERL string increment feature to achieve the aforementioned goal. > However, I believe the benefits of aligning the behaviour of the > increment/decrement operators with addition/subtraction are larger than > keeping support for the PERL increment, which in its current state has > various shortcomings. > > Best regards, > > George P. Banyard > I don't see a section in the RFC about JIT or anything related to OpCache, but I know from experience with the Operator Overloads RFC that there are several architecture specific assembly optimizations for ++ and --. Have these been considered, and how will they be impacted? Jordan --00000000000091550905f2b7451b--