Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116230 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 21985 invoked from network); 5 Oct 2021 16:10:58 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Oct 2021 16:10:58 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 075B5180564 for ; Tue, 5 Oct 2021 09:55:26 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_NONE 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-oo1-f41.google.com (mail-oo1-f41.google.com [209.85.161.41]) (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 ; Tue, 5 Oct 2021 09:55:25 -0700 (PDT) Received: by mail-oo1-f41.google.com with SMTP id i26-20020a4ad09a000000b002a9d58c24f5so12361oor.0 for ; Tue, 05 Oct 2021 09:55:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20210112.gappssmtp.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1kK2bwTc2ZxfFuYd1Jno7oDKhYswKNZ6Or3h+nvYcbI=; b=JgtA+fUl8R1/2vYcTHyitfBF/IqgVpnT0HpPyLsuEzR4cWG0Xw121w8eUem0QC9NMd 9tGeqj59OynXF4WeLz6Z7oX9dJz65xGAkjwl/j/LVw7aXEjKSZT5ywXfHLVtzo/AZaeb 3KN60qUen/hTO4VH8fkgncFSQ3H079JUge9hnqN7JTrT0Xr62CRLS7AoI5WA60jIFsZp aL3qbWhBl/sH8qup6SRcQdmCzUF48Qm53c5yMH+qLAmrAxUCq4ib/IZ7jZCVKJ1mdWgt etLSf8CFnZRF9xDS+4gbdyrU2nOGnB7ePzldXJzo9vezx/SfDJ9tXSw3FDSuOs3+gszU /3zg== 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=1kK2bwTc2ZxfFuYd1Jno7oDKhYswKNZ6Or3h+nvYcbI=; b=AjEdEMQVqsYf4cDapUWRtkbj6fqFi1RrnTIJokLM/gkU6BEdx+QKqE58CBhE5+0hG4 ftA55xtUUQPB6Yr/cIFdAncBlzVJuCLKPJ5DTONXvHKqj1g03RPPCtiGbpV6RKdMz7fa Hw56aLWXN/SQzx+CF0YmyTP8D2dtmQtwD4QlDkW5WeHA2qO/I9r66wijfaZsz9CGbVxY ZsWrpfkNgF5m7Ei7Ai67ZW23UK4FtGQCGFlKKEmxnJxSvTCnkg+PvGeaQQbYXgIgbbMS zn9TxzlVK1KsEplvuEH7suVwdHamPLcc1CdDibDsXAgCnl0RL3YEWv3ZHkHGhVN/9RsD ACzA== X-Gm-Message-State: AOAM530NeBsf2uF1qLWJNsRsNqypGWJYtCtkm5W5SemNUxSgQCbplCYz bugc2ilR13IXFA9NwjMEEzb9nA== X-Google-Smtp-Source: ABdhPJzliIwnWYvveGDh22deO26L8s7blMZdOO0kDOzgZHvEM1WwF4Ux8ZJtSHXJ4Ur29F8CkUIOSg== X-Received: by 2002:a05:6820:1612:: with SMTP id bb18mr14335331oob.7.1633452923485; Tue, 05 Oct 2021 09:55:23 -0700 (PDT) Received: from [192.168.1.10] (c-24-98-254-8.hsd1.ga.comcast.net. [24.98.254.8]) by smtp.gmail.com with ESMTPSA id d4sm3645771oth.47.2021.10.05.09.55.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Oct 2021 09:55:22 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) In-Reply-To: Date: Tue, 5 Oct 2021 12:55:21 -0400 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: References: To: "G. P. B." X-Mailer: Apple Mail (2.3608.120.23.2.7) Subject: Re: [PHP-DEV] [RFC] Allow null as standalone type From: mike@newclarity.net (Mike Schinkel) > On Oct 2, 2021, at 11:06 AM, G. P. B. = wrote: >=20 > Hello internals, >=20 > I'm proposing a new RFC to make 'null' usable as a standalone type. >=20 > RFC: https://wiki.php.net/rfc/null-standalone-type Regarding the RFC's proposed disallowing of `?null`, is that really = needed? Obviously it doesn't make sense for a developer to write that, but I = could see that a code generator would have add special-case logic to = avoid outputting `?` with the type `null`. Does it hurt anything if it is allowed? -Mike