Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126325
Precedence: bulk
MIME-Version: 1.0
References: <CAJWOiuNQ+ue-ZyY3EfnEQGo9JJ5mjf=tByxp31M__N71_ODy6A@mail.gmail.com>
In-Reply-To: <CAJWOiuNQ+ue-ZyY3EfnEQGo9JJ5mjf=tByxp31M__N71_ODy6A@mail.gmail.com>
Date: Fri, 7 Feb 2025 14:21:36 +0500
Message-ID: <CALWFqqBFJr2E-8s7eGsZ=MOFGpaa7rsgcqrSU0QB5g6zs_yRdQ@mail.gmail.com>
Subject: Re: [PHP-DEV] RFC: Not Null Assertion Operator
To: Mihail Liahimov <91liahim@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
From: ilyaorlov124@gmail.com (MrMeshok)

>
> Examples of potentially using in PHP:
> Without this operator we writing this code:
>
> $foo = ...
>
> if ($foo === null) {
>     throw new FooIsNullException();
> }
>
> $foo->bar.
>
> With this operator:
>
> $foo!->bar
> $foo!->someProperty->method();
> $foo!->someProperty->anotherProperty!->method();

I see where you're coming from, in my code I had to deal with a lot of
APIs with models which have nullable properties, but they shouldn't be
null if some conditions are met.
So I work with them in this way
```php
if ($response->code === ResponseCode::Success) {
    // order and quantity are nullable
    return $response->data->order->quantity ?? throw new
UnexpectedResponseException($response);

    // With method calls you would need to add nullsafe operators
    // order and date are nullable
    return $response->data->order?->date?->format('Y-m-d') ?? throw
new UnexpectedResponseException($response);
}
```
UnexpectedResponseException is just an exception that keeps faulty
response, so I can catch it and act on it, or it just gets logged and
I can show producers of API that they have a problem.

I see a point in !-> operator if it would work just like that. Throws
a specific error that has an object that triggered this error.