Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115565
MIME-Version: 1.0
References: <CAOWwgp=B7-AvMao0POCF_h_A3A4voHNA_BsjfonBQ8yDHb0v-A@mail.gmail.com>
 <BN7PR05MB4033B26F14CF1726EFFE810ADEE59@BN7PR05MB4033.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB4033B26F14CF1726EFFE810ADEE59@BN7PR05MB4033.namprd05.prod.outlook.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Fri, 23 Jul 2021 09:56:07 -0600
Message-ID: <CAAKU0u=aznvHDBeQoPJoMUhHtDjDzKkMDxdcvPTNC7WT7Yb2AQ@mail.gmail.com>
To: Theodore Brown <theodorejb@outlook.com>
Cc: Nicolas Grekas <nicolas.grekas@gmail.com>, PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Nullable intersection types
From: internals@lists.php.net ("Levi Morrison via internals")

> As you note in the RFC, PHP already defines `|` as having a lower
> precedence than `&`, so `X & Y | null` can only be interpreted as
> `(X & Y) | null`. This is consistent with other languages such as
> TypeScript, where `A & B | C & D` is parsed as `(A & B) | (C & D)`.
> [2]
>
> Since precedence is already defined for this syntax consistently with
> other languages, I don't think it's necessary to require parentheses
> if we use the `A & B | null` syntax.

I want to acknowledge and reject this. Few people keep the bitwise
precedence information in their head. It's not worth it -- just
require parenthesis.