Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107663 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41144 invoked from network); 24 Oct 2019 19:59:56 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 24 Oct 2019 19:59:56 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id D8BA02C3806 for ; Thu, 24 Oct 2019 10:46:22 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS36024 206.123.114.0/23 X-Spam-Virus: No Received: from mail1.25mail.st (mail1.25mail.st [206.123.115.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Thu, 24 Oct 2019 10:46:22 -0700 (PDT) Received: from [10.0.1.6] (unknown [49.48.241.119]) by mail1.25mail.st (Postfix) with ESMTPSA id 522BC60373; Thu, 24 Oct 2019 17:46:13 +0000 (UTC) Content-Type: multipart/alternative; boundary=Apple-Mail-92A195A0-7DE8-4642-85A4-6310D7BAC6A1 Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (16G102) In-Reply-To: Date: Fri, 25 Oct 2019 00:46:08 +0700 Cc: Ken Stanley , PHP internals Content-Transfer-Encoding: 7bit Message-ID: References: To: Dan Ackroyd X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] anti-coalescing-operator From: php-lists@koalephant.com (Stephen Reay) --Apple-Mail-92A195A0-7DE8-4642-85A4-6310D7BAC6A1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > On 25 Oct 2019, at 00:33, Dan Ackroyd wrote: >=20 >> On Thu, 24 Oct 2019 at 18:21, Ken Stanley wrote: >>=20 >> Since PHP 7.0 brought forward the Null Coalescing Operator (??), writing >> more succinct code for how to handle null values has been a blessing. But= , >> what about the inverse when you want to do something when a value is not >> null? >=20 > Hi Ken, >=20 > It may help to give a real world example, rather than a metasyntactic > one, as I can't immediately see how this would be useful. >=20 > People have been expressing a concern over 'symbol soup' for similar > ideas. The null colalesce scenario happens frequently enough, that it > seemed to overcome the hurdle needed for acceptance. Again, giving a > real world example of what you currently need to do frequently might > help other people understand the need. >=20 > cheers > Dan >=20 > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >=20 Hi Ken, This sounds like an alternative approach (for solving the same basic problem= ) to the nullsafe operator discussed a while back, no? https://wiki.php.net/rfc/nullsafe_calls Cheers Stephen=20 --Apple-Mail-92A195A0-7DE8-4642-85A4-6310D7BAC6A1--