Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126912
Precedence: bulk
MIME-Version: 1.0
References: <010f0195c30f8ccb-c7fa839e-ec18-4613-9851-9d96b943dca2-000000@us-east-2.amazonses.com>
In-Reply-To: <010f0195c30f8ccb-c7fa839e-ec18-4613-9851-9d96b943dca2-000000@us-east-2.amazonses.com>
Date: Sun, 23 Mar 2025 13:37:48 +0000
Message-ID: <CAGBsUrdwNqRcu4qOuDDPy7Hh=8VngfgJsaDza_q-3FB2LxfREg@mail.gmail.com>
Subject: Re: [PHP-DEV] Feedback for nullc Idea
To: Robert Chapin <php@miqrogroove.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
From: tekiela246@gmail.com (Kamil Tekiela)

On Sun, 23 Mar 2025 at 12:52, Robert Chapin <php@miqrogroove.com> wrote:
>
> Hi PHP folks,
>
> I submitted a proposal on Monday that received no replies.  The idea was
> about adding a functional construct nullc() that could act as an inline
> null coalesce for a variable.  That task is currently not possible in a
> nullc() user function, but instead requires an expression like ($var ??
> null) with mandatory extra parentheses.  A functional expression could
> make this less prone to mistakes.  It would also avoid concerns with
> alternatives such as unary operators.
>
> Any feedback on this idea would be appreciated.
>
> -------------
> Robert Chapin

Hi Robert,

For some reason, your emails are classified as spam. I am attaching
the link to your previous email for the record.
https://externals.io/message/126826

Regards,
Kamil