Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115135
To: Eugene Sidelnyk <zsidelnik@gmail.com>,
 PHP Internals <internals@lists.php.net>
References: <CAM0Ccxh0U5ETmfDJqru3m-1406asn53DEoJMP+ip9KYbKngjng@mail.gmail.com>
 <CAM0CcxjAgShTu6rPCVdzfRMzsM48HviYWghRyPNf5p3gX_GBiQ@mail.gmail.com>
Message-ID: <929ae0be-fc39-1444-8912-170e2f5fd840@processus.org>
Date: Fri, 25 Jun 2021 09:17:30 +0200
MIME-Version: 1.0
In-Reply-To: <CAM0CcxjAgShTu6rPCVdzfRMzsM48HviYWghRyPNf5p3gX_GBiQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: [PHP-DEV] Re: Nullsafe Types
From: pierre-php@processus.org (Pierre)

Le 25/06/2021 à 08:58, Eugene Sidelnyk a écrit :
> I would really like to hear your thoughts on this.

Hello,

As being a user of more than one language, in which at least 2 have the 
same nullsafe operator (PHP and TypeScript), I'm used to this syntax, 
it's clear about the intent at the cost of a single char.

It places the nullsafe intent where you actually use it, instead of 
making it implicit on a whole composition chain, which would then create 
nullsafe behavior to be "always on" in the whole composition chain and 
very (very) hard to debug.

I think this would create too many side effects.

Moreover, your proposed syntax is very hard to read, in my opinion, and 
will probably cause confusion.

Regards,

--

Pierre