Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119383 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 22877 invoked from network); 20 Jan 2023 18:48:47 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jan 2023 18:48:47 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E19161804D4 for ; Fri, 20 Jan 2023 10:48:44 -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=-1.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,HTML_OBFUSCATE_05_10,RCVD_IN_MSPIKE_H2, 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-yw1-f174.google.com (mail-yw1-f174.google.com [209.85.128.174]) (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 10:48:44 -0800 (PST) Received: by mail-yw1-f174.google.com with SMTP id 00721157ae682-4c24993965eso85003097b3.12 for ; Fri, 20 Jan 2023 10:48:44 -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=YOrT5kZKZmwDUVcRctqSBDreF3l3yvLDqqXnHqb1GLI=; b=Ognoa+66n/wkgQkkxEBBySRsGMapIKMlQ2LrAoDJLV483zw+tfSC1PB0Tpl3Aw0x2f R01wAzLoSG0gyvgN+oSiZVIp6Pdrza9uRSGiD756Lg+hpVLT9DCGKVxEOm0MQghbO1VI NBcYwYLXqQw2CKRebuVVhEyllaHSJZBtUhkijOCPS65jXVPGyd6Zl/zVBYBhTlZ3Ssty xLjGv0KUkGLnL8niBxd02mjuN2sd/2TzkbMbFSPYdE2tv4SvTQdmYNJ9Dvj3XYZVIfCq 62HA6eLSeMEzAakCj6rLbO3WL/L+fCRDp5BMAmWRIv6bDcmidRW6Zzu3oKmRuyltcuuC 7qag== 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=YOrT5kZKZmwDUVcRctqSBDreF3l3yvLDqqXnHqb1GLI=; b=Atve0fQ2fL4zbRDH2NJV5q3gf/kJn+EKBP5TZAfo+up4j5B2Yj5JK63d5h0LPyF0q4 Qog5cdbGwXrMgaT/EUUUcGnBS+scijaKwkIPADemicpwaGr1ko4xhWqkyzUxS2E1h3tV WDB4FllSs9mmxqaz4xcMjq20wDU4xu5bnNbFf1si++BiYVOWiNAHgQpYkkGJmKIBBMdN pjVaCjhJET8Tn5Ufa78F/Ejnba4L00qtSDzW7b8VbTcC7q4SVA1Q1jb4QurJp6OtVRy3 oOw4JuQPnN9m1SRqymvH8JGeLnTbR+gOk6vmjcz4wv7I2dHbXLJDs7ruAMFtjzKgd021 d75A== X-Gm-Message-State: AFqh2kq9N0p0mTzRb/ZNzlhp0mu8z1A4fKv+dPzkVm8ebzTvWHCZP9Fn 2MClxYRO8JtZuaPGpB45CPkvNfmFIxdaSOFg6/MXhQ8ROp4= X-Google-Smtp-Source: AMrXdXtYDzi5/wy81J16RsrlUEPTXEFllx/XzW7HIPXVP91XyD0+2HomBGJAOySyRmwd8+iv5S/Sv04inC2U/crKd2o= X-Received: by 2002:a81:70d7:0:b0:4da:4e12:f6cb with SMTP id l206-20020a8170d7000000b004da4e12f6cbmr1945440ywc.398.1674240523806; Fri, 20 Jan 2023 10:48:43 -0800 (PST) MIME-Version: 1.0 References: <5FC8DBAF-8D78-4E94-A3B0-3BDED3A3E53C@craigfrancis.co.uk> <789af205-4582-66a9-694a-10e18b8b9f56@demon-angel.eu> <9d225219-4e31-b362-52a9-9a298a0a55ef@telia.com> <768de46c-9ff2-eee2-24ab-e78e27ad167c@demon-angel.eu> <828f1ec6-e8ff-01b2-dc0e-a6cf1dd16eb2@demon-angel.eu> In-Reply-To: <828f1ec6-e8ff-01b2-dc0e-a6cf1dd16eb2@demon-angel.eu> Date: Fri, 20 Jan 2023 18:48:33 +0000 Message-ID: To: Mark Baker Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="000000000000b0abff05f2b67f42" Subject: Re: [PHP-DEV] [RFC] Path to Saner Increment/Decrement operators From: tekiela246@gmail.com (Kamil Tekiela) --000000000000b0abff05f2b67f42 Content-Type: text/plain; charset="UTF-8" I don't think it's such a huge issue as you make it to be. The documentation states this only as an alternative: https://phpspreadsheet.readthedocs.io/en/latest/topics/accessing-cells/#looping-through-cells-using-indexes It also mentions the pitfalls. I doubt many users would prefer that "alternative" given that the recommended way is simpler and does the same thing. I also don't think that performance would come into play here. Any difference would be insignificant. I believe that the benefits of the deprecation outweigh any potential extra work the developers may have. --000000000000b0abff05f2b67f42--