Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117813 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 40560 invoked from network); 28 May 2022 05:27:41 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 May 2022 05:27:41 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id C490F180053 for ; Sat, 28 May 2022 00:10:50 -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=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, 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-wr1-f43.google.com (mail-wr1-f43.google.com [209.85.221.43]) (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 ; Sat, 28 May 2022 00:10:50 -0700 (PDT) Received: by mail-wr1-f43.google.com with SMTP id e2so8429733wrc.1 for ; Sat, 28 May 2022 00:10:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=craigfrancis.co.uk; s=default; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2YxUpgx5LwnLusPeB1KsnnpaLUfioMjZLiquev8MmJU=; b=XKaQiw6v0anOMFVY2k+pKJMl/XISDdRo+yMvfht+rneGK0HTxznfXMd7uowjHIx8X2 vxkYyE/J2Dl7jPcgbAoIZ2MmMDJpSS8L297ak3buv8A+V0gttB7Al2DZn3mmk6L29lMi op060oD9v77EVMMMQyOz/ZjdjZFd6ujjU0KsY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2YxUpgx5LwnLusPeB1KsnnpaLUfioMjZLiquev8MmJU=; b=exAtGFyv9sWU2WK2ktDYTn3F/uGHtF6gje8v3ZwU1FM++shaCSHJjahsWSXBJmWDDV sLZFhQqzVrS8pDLJsdbycL/6chjCsvwk1FiVN4FlaznRktnLHaaehoCM9JM7vlrx2LTQ 8TobHexlqoWfEgK9iuMfK1/qBC9UeuIiCvTiK96EbmCJoxYltjUtovqbnDvkF/vgxOSh O5E/Gdezls+fyV6PrlcHfAlcLwFSjbjVF9C6QKgfLMx8yViw5iHtBSsL5xggESguF96A Yg1EoRASH7u3Gt2TbRqMkX8ml3c7apbELrMDh9ul24Uf44RsbxUaLPSuqbod4cVK6scY bAOA== X-Gm-Message-State: AOAM532pCNnJhi5yTF+Y2tzTOK/f2ZZRB9WscE+qneqefOoCz1i/J6zD weL9vBCQzVMUzkzGFlOjum9vXA== X-Google-Smtp-Source: ABdhPJxm5YYM4TvqnpzB1P8fhCjSm5yXA8bDeofDRTO24lchExw2V27tvfRpaKd03eS3BJD7YDGJ+w== X-Received: by 2002:a05:6000:1541:b0:20f:f91a:2095 with SMTP id 1-20020a056000154100b0020ff91a2095mr16038857wry.80.1653721848915; Sat, 28 May 2022 00:10:48 -0700 (PDT) Received: from smtpclient.apple ([94.173.138.98]) by smtp.gmail.com with ESMTPSA id m1-20020a1c2601000000b003942a244f2fsm4223733wmm.8.2022.05.28.00.10.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 May 2022 00:10:47 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) In-Reply-To: Date: Sat, 28 May 2022 08:10:44 +0100 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: References: <2B63A776-11B9-49BF-AE0A-FCF7F4E738F2@craigfrancis.co.uk> To: Aleksander Machniak X-Mailer: Apple Mail (2.3696.100.31) Subject: Re: [PHP-DEV] NULL Coercion Consistency From: craig@craigfrancis.co.uk (Craig Francis) On 28 May 2022, at 07:25, Aleksander Machniak wrote: >=20 > On 28.05.2022 04:36, Craig Francis wrote: >> On 8 Apr 2022, at 18:34, Craig Francis = wrote: >>> I've written a new draft RFC to address the NULL coercion problems: >>> https://wiki.php.net/rfc/null_coercion_consistency >> I give up. >=20 > Don't give up. You have my Yes vote. >=20 > Imo, the RFC: > - fixes real upgrade problem (very important), > - improves consistency in a better way than the solution introduced in = 8.1. > - does not change strict_types behavior >=20 > Some people don't care with what arguments their functions are called = with. As long as the value can be coerced to the expected type the = function will do what it is supposed to do. Other people have = strict_types. All people don't want to be forced to modify a working = code. >=20 > So, this is another "battle" between strict and non-strict camps. I'd = like to see which is the majority these days. I hope that even some = strict-code proponents can see this makes sense. I'm sorry Aleksander. While I think this is the best approach as well, I don't have a vote, = and I don't have the time/energy to respond to emails where I'm clearly = not making any progress, or doing a good job of putting the case forward = (for reference, each email usually takes a least an hour, as I want to = make sure I've completely understood what the person is saying, and yay = dyslexia). Anyway, I'm going away for a week (leaving in 1 hour), and when I get = back, I *really* need to focus on other things (life, client work, and = things related to `is_literal()`/`literal-string` which I am making some = good progress on). Thank you for your comments though... and maybe you would be able to = convince the other voters it's worth it? Keep in mind, even my quiz from a few months ago had split the room on = this issue: https://quiz.craigfrancis.co.uk/ Craig