Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110966
Message-ID: <E9BE1364-26DA-42EF-8448-77ACF574594D@joshbruce.dev>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_72FD6BA7-7CA2-41E7-82C3-E324154CFFF6"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Sun, 12 Jul 2020 12:35:21 -0500
In-Reply-To: <bd94ee30-7871-4686-b43d-f1299f5371cc@www.fastmail.com>
Cc: php internals <internals@lists.php.net>
To: Larry Garfield <larry@garfieldtech.com>
References: <65EE4215-3F80-435C-B271-DBE30D26E2CB@joshbruce.dev>
 <bd94ee30-7871-4686-b43d-f1299f5371cc@www.fastmail.com>
Subject: Re: [PHP-DEV] [CONCEPT][DISCUSSION] Instance as boolean
From: josh@joshbruce.dev (Josh Bruce)

--Apple-Mail=_72FD6BA7-7CA2-41E7-82C3-E324154CFFF6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>=20
> Focusing on Bool is, I think, a good choice because it has an argument =
for it other than "well it works for strings."  You hint at it in the =
writeup but really bury the lead: Null objects.
>=20
> Being able to not use null or false as a "not found" case and instead =
return an "empty" value object is very nice, but then you also want to =
know if the value returned is legitimate.  An object that could =
self-cast to boolean makes something like this viable and type-safe:
>=20
>=20

Thanks!

I think you=E2=80=99re right - maybe just taking a minute to figure out =
what the lead was. lol

I updated the repo and link: https://bit.ly/php-0002 =
<https://bit.ly/php-0002>

Going to be starting a new thread with subject that matches better where =
we are:

Objects able to define emptiness (and possibly truthiness by extension =
to maintain consistency - but object may be an exception??).

Cheers,
Josh

ps. Also did get registered to the wiki from a different thread =
conveniently happening at the same time. :)=

--Apple-Mail=_72FD6BA7-7CA2-41E7-82C3-E324154CFFF6--