Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107681 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 33037 invoked from network); 25 Oct 2019 01:41:50 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 25 Oct 2019 01:41:50 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id DCBF42D1FE8 for ; Thu, 24 Oct 2019 16:28:20 -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, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No Received: from mail-qt1-f193.google.com (mail-qt1-f193.google.com [209.85.160.193]) (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 16:28:20 -0700 (PDT) Received: by mail-qt1-f193.google.com with SMTP id e14so555222qto.1 for ; Thu, 24 Oct 2019 16:28:20 -0700 (PDT) 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=z9C7UG1y2eK8QMaq2J7WPdR0FfTmd75z+DsBQNJFv+s=; b=bhL62jQV30gPwmOjLfpvpTcT1+Oc/MIoifdrNAyS7DL+c48sDliPKQYxsvYWEk+wvt 8JSBdjn63hpAEHRw2tpqW1+lbsVk0aM25z/T03lqR+tsqep1HAytfFuUwz7bSSgojjrD 8xxMZ+7/+jJ5KK3c81dZkCBp1T7+M7tBEdEpFl0TcV5R5rIroDo3PoIkEmvqHyJDI1Vb +V8PwoKba3r+fcyV4sNDHt5s+EnqsC0cnCS6RBOgVIGOL+zzXcscboZo15eTobHN/KGg DS28cIXPQwJ/oBs8riKzWYVAsxKKTK8r7pbLP5MPj3wxvy/l3MJJTqgiURQUMG385vkT i2/A== X-Gm-Message-State: APjAAAWBq7M56297QOMfeHWOaYiGZCNjbENlWuxSbc23Fddu35cc/Yrr 0c0fdMVUkTBfUtFlQhKcNFIetAbQMf0g/MszFANYLw== X-Google-Smtp-Source: APXvYqxGnkPs7LEJRqju9uKoNbZKRYceZNyLIR9bKxp1EqL5gr54HHezsX3CS/dTI8WjKYVBnxBe5HX+IMsS8aJw72E= X-Received: by 2002:a0c:92dc:: with SMTP id c28mr550419qvc.26.1571959700221; Thu, 24 Oct 2019 16:28:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 24 Oct 2019 18:28:01 -0500 Message-ID: To: Stephen Reay Cc: Dan Ackroyd , Ken Stanley , PHP internals Content-Type: multipart/alternative; boundary="0000000000008884a10595b063b8" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] anti-coalescing-operator From: pollita@php.net (Sara Golemon) --0000000000008884a10595b063b8 Content-Type: text/plain; charset="UTF-8" On Thu, Oct 24, 2019 at 12:46 PM Stephen Reay wrote: > 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 > > At the risk of hijacking, @matthewrask asked me about ?-> a couple weeks ago (Javascript is making this one popular), and I threw together a rough PoC at https://github.com/php/php-src/compare/master...sgolemon:null-coalesce which I suspect he intends to RFC properly soon. As long as the topic is at hand, what's the general appetite for it? Should I bother polishing the turd? -Sara --0000000000008884a10595b063b8--