Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115750 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 40198 invoked from network); 16 Aug 2021 07:13:30 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Aug 2021 07:13:30 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B01E81804B4 for ; Mon, 16 Aug 2021 00:45:23 -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 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-f43.google.com (mail-ot1-f43.google.com [209.85.210.43]) (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 ; Mon, 16 Aug 2021 00:45:23 -0700 (PDT) Received: by mail-ot1-f43.google.com with SMTP id v33-20020a0568300921b0290517cd06302dso7140395ott.13 for ; Mon, 16 Aug 2021 00:45:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SvCxQhDK1EjaUZQz15tQ4y0ScgVUQ+LP9A97E+MXsB4=; b=JtUqU4Ob4jXJuc05WTeyADCAw8U35Rdzdzr+VS0kSVeQ3nBJSbf8HP6CkNkDRvMJwc 9jy5Myd32c0ljkVuzWW71IM55ogl8u2a0+EztoFl5B9EDEMVJtJiCXnDaX1V8rDuzIsO +u8c7V8WVMxCh0mi8yTjA1YDaxOYhbEFITYz/RhCN80F/NAskSvmmM0gbQ3b1+bnNprP BXL8c3xyrRKGH1qX4+4M1bAVoP03abGHE5mFAuYeIil3vk3ESzdeinWZ3X6uNKBCJ6Qo E3w9yzHRm1tRz6n2F4CubQe8tx1cQTp6yUKBaGJA9mA7pvR09S9fTZVcKkc5VwRhfN12 Xghg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SvCxQhDK1EjaUZQz15tQ4y0ScgVUQ+LP9A97E+MXsB4=; b=WA+0v1kbw+g50I95L9OT1/dmsI40JG+dzpjVfwzBRAaAt2ObF8lEjX9+KhsdyumAc0 Zr6nIt3Z4lmiZ+YPy92yLnVAQD8wNP+MbJwCM2fOOluE0of2ukbg+ABO5xbEiPwOVJ6W Q2M2MGKpF4XqcMSAl6uLhJTCxJGV2lZCuEIX42VPAK5NvD5lQ3+AO9NX2hJQsK9MJeSl 6XxnUstcFMYZMFBZqKQsaiB9/5ijfxxxt4Yg7y4SMbrj47ezGAVDtcgXJb6sQAYifYFz U+UPRBvIxaXReeHVgY+Yco6s4XsVk9+pvddi41LuthJcLcrNC3TGL7RRF/qq4lf25TGK G78A== X-Gm-Message-State: AOAM5326a/iXZNATas4myz9S/gqNAqZIVoFC40qrcJgn4kXgCMIfrTO0 BoHglyEW2cXJMN9ZNGRAz/xD6MIwOmafu0MHf1Y= X-Google-Smtp-Source: ABdhPJytMfl4SHXEw4Up8EuO525wzPpkQ6Csay6q2gMogFEKHLW8LEarO8J8wUnJON6JBJ6w9jz9Im2zE1INMUFzy+Q= X-Received: by 2002:a05:6830:2006:: with SMTP id e6mr11996305otp.257.1629099922364; Mon, 16 Aug 2021 00:45:22 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6839:755:0:0:0:0 with HTTP; Mon, 16 Aug 2021 00:45:21 -0700 (PDT) In-Reply-To: References: <72785D6F-6803-49BB-B575-01061699ABF4@gmail.com> <448DAADA-C819-457F-ABBF-F942128B2830@gmail.com> Date: Mon, 16 Aug 2021 09:45:21 +0200 Message-ID: To: Deleu Cc: Tobias Nyholm , Kalle Sommer Nielsen , Patrick ALLAERT , Nicolas Grekas , PHP Internals List , Ben Ramsey Content-Type: multipart/alternative; boundary="0000000000002d1c5205c9a86247" Subject: Re: [PHP-DEV] [VOTE] Nullable intersection types From: krakjoe@gmail.com (Joe Watkins) --0000000000002d1c5205c9a86247 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Morning all, The initial RFC was clear that nullability was not supported, however that doesn't seem to be have widely understood. When I said we should move forward I did imagine that there was some consensus about the syntax we should use if we were to support nullability. As this conversation has progressed it has become clear that we don't have that consensus, and many people are just not comfortable trying to build consensus this late in the cycle. The RFC is not passing currently so I don't think we actually need to do anything, except prepare to deploy the feature that was voted in, pure intersections. The RFC should be allowed to complete, it's gathering important data. In the end, I'm not as happy to make an exception as I was when the discussion started. Cheers Joe On Monday, 16 August 2021, Deleu wrote: > > On Mon, Aug 16, 2021 at 2:22 AM Tobias Nyholm > wrote: > >> Hey. >> >> > No mistake: the "pure intersection types" RFC was explicitly designed >> to avoid scope creep (this RFC). >> >> >> Just because it was intentional, does not make it less of a mistake. >> I see that we have different views of this. And I understand that you ar= e >> happy with this change, but only for 8.2. >> >> > I hope one day I'll have built up so much experience, knowledge and > confidence to call a 30 x 3 vote of the selective people that can cast a > vote "a mistake". > > -- > Marco Aur=C3=A9lio Deleu > --0000000000002d1c5205c9a86247--