Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110882
MIME-Version: 1.0
References: <65EE4215-3F80-435C-B271-DBE30D26E2CB@joshbruce.dev>
In-Reply-To: <65EE4215-3F80-435C-B271-DBE30D26E2CB@joshbruce.dev>
Date: Wed, 8 Jul 2020 14:54:33 -0300
Message-ID: <CAOsHV+s3=cyv=Q38uAJ35DyP_LUjjmzTNEx3ivH_W0jR_pOzpw@mail.gmail.com>
To: Josh Bruce <josh@joshbruce.dev>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [CONCEPT][DISCUSSION] Instance as boolean
From: marcio.web2@gmail.com (Marcio Almada)

Hello Josh,

> Link to working draft: https://bit.ly/php-0001 <https://bit.ly/php-0001>

From a type safety POV I'd prefer to have an interface available, the
same way we did
to the Stringable interface RFC. But I'd rather keep these engine
affecting behaviors
with the same magic method naming conventions and its `__` prefix.

So `implements Bool` + `function __toBool() : bool` is the only path that s=
eems
entirely consistent with what we already have.

The draft doesn't mention (bool) casting behavior at the time I'm
reading it, but you do
mention the possibility. It seems necessary to me. Why wouldn't
`(bool) $my_bool_obj`
behave differently from `(string) $my_stringable_obj`?

>
> ps. If you have any feedback or information on social interactions here t=
hat might help, please do let me know, normally I would have watched for a =
while before putting my foot in - hopefully it doesn=E2=80=99t end up in my=
 mouth. :)


Thanks,
M=C3=A1rcio Almada