Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111010
MIME-Version: 1.0
References: <21C5073D-3F39-49DA-8686-E027AE780793@joshbruce.dev>
In-Reply-To: <21C5073D-3F39-49DA-8686-E027AE780793@joshbruce.dev>
Date: Wed, 15 Jul 2020 00:48:05 -0400
Message-ID: <CAKuGYLT-31Bjav6bKBYDBqPc6wb41FzebzoSWBmt9+4=OdRAYA@mail.gmail.com>
To: Josh Bruce <josh@joshbruce.dev>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d7793405aa73a131"
Subject: Re: [PHP-DEV] [RFC][Discussion] Objects can be declared falsifiable
From: matthewmatthew@gmail.com (Matthew Brown)

--000000000000d7793405aa73a131
Content-Type: text/plain; charset="UTF-8"

On Tue, 14 Jul 2020 at 19:59, Josh Bruce <josh@joshbruce.dev> wrote:

> Implement an interface and magic method to allow objects to represent
> false (or empty) while still be valid instances of the custom object (type).
>
> https://wiki.php.net/rfc/objects-can-be-falsifiable <
> https://wiki.php.net/rfc/objects-can-be-falsifiable>
>
> If you saw the latest from this morning, not much has changed except
> hopefully improved formatting and now being the official mix of things.
>
> If this is your first time, the cues are taken from:
>
> - __toString()
> - Stringable
> - and __toArray() (not accepted or approved yet)
>
> Thank you for all the feedback and patience so far, appreciate it!
>
> Cheers,
> Josh


I'm not sure I love this (mostly from a static analysis standpoint).

It means that there would exist some `$foo` with the property that `$foo &&
!$foo` evaluates to true.

That seems to be a bad place for a language to go, and it would increase
the false-negative rate of static analysis tools.

--000000000000d7793405aa73a131--