Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107662 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 36695 invoked from network); 24 Oct 2019 19:47:24 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 24 Oct 2019 19:47:24 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id ADB3F2D1F81 for ; Thu, 24 Oct 2019 10:33:51 -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,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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:33:50 -0700 (PDT) Received: by mail-pl1-x633.google.com with SMTP id q15so12191743pll.11 for ; Thu, 24 Oct 2019 10:33:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+ME/jfuhXnooL2nwHf6jFg2k/y4DDItrRVs5uVU7iyg=; b=IEX0iXuR+PTX942dbVIEQI45mtsGbQF+GGDgm/Xfpjc56WFWt88qgeABl3i8lUt90y jZydXUkTrordxc92nkdoBn3gtku6TCdyQVom2Es+MhmEOp4exsM1yfFLhyvh19tjdQdX bnlQqtBLitj1V9ExfY6Bbo68yGm0EIh3GASs87v4MtxNKU7V9CeQT+JQr1GhStKaC5p9 Wo6ogyCppQ0thfttVqjFotGgUahygl1MnsvAfOlWellMKtR+YQJXl1ysquUlJ0YynijB ZIoFNfzWZFKBrwZ3q6Ew7p2xCQb8uEL7KOQ2HeG9AtMyD7nCZwl/zsMnglphUymeuswv RLgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+ME/jfuhXnooL2nwHf6jFg2k/y4DDItrRVs5uVU7iyg=; b=WugrI7VtE54MJ0K5HbeS1HFASJ+ZdFPBWMl6/IDXIsbMuPDMpw0qP6dMBJHveGJ4+g YtToQtg+HZAnf9sr3RDgLZxep9bGEEFbgDOCwns9WkqpX/xBDDN7TJZ0lQMWZU44TMJs 6ilyMA9uVxI1Wj91V9T7MGYrXYy4iXZTU2XJBRptBvoRpCVGKE6SxsJWiS1rHZDZNheJ 7UKdkq8KE8cAC420I5aBEc2ikdAfqcbEipqzAAZ3CK0L52TsrZIoI4KkdwDAEw1gSlsT 92/F6YerXuOSggGTLUUFaMFNH6m9Hyy8gj84AZsIoXf8SyfHF9mOThXyheWzckSOPAPv abIA== X-Gm-Message-State: APjAAAU+z+RJ7GEVrdaOOC7BHzCUtcMB4SW7MJT+UZI9ZlQfDlvU9bGs AUUSBB/ifSa+foUgfQ4a1fg0cZndjDzz2H+3EJXbzQ== X-Google-Smtp-Source: APXvYqyiRReoHvIc41UVYx+SBcmXlvwGqgTNK0rPBISkeYGyfuwW2bWkH8/uqWrJOpqe1sLL5NoDo/yTtOlzVEBfhqs= X-Received: by 2002:a17:902:9a44:: with SMTP id x4mr17261154plv.127.1571938430018; Thu, 24 Oct 2019 10:33:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 24 Oct 2019 18:33:39 +0100 Message-ID: To: Ken Stanley Cc: PHP internals Content-Type: text/plain; charset="UTF-8" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] anti-coalescing-operator From: Danack@basereality.com (Dan Ackroyd) On Thu, 24 Oct 2019 at 18:21, Ken Stanley wrote: > > 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? Hi Ken, 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. 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. cheers Dan