Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129901
Feedback-ID: id5114917:Fastmail
Date: Fri, 23 Jan 2026 16:34:55 +0000
To: php internals <internals@lists.php.net>
Subject: =?US-ASCII?Q?Re=3A_=5BPHP-DEV=5D_=5BRFC=5D_Deprecate_Fuzzy_Type_?=
 =?US-ASCII?Q?Casts_and_Allow_Stringable_in_Strict_Mode?=
User-Agent: K-9 Mail for Android
In-Reply-To: <53f11b44-11c1-4b23-a8be-c7846262a49c@app.fastmail.com>
References: <CAMU7ir+1VfQCiSVG0BjN5V+upNU2kU+a_rKDXO1=Ahu3ndmOGg@mail.gmail.com> <53f11b44-11c1-4b23-a8be-c7846262a49c@app.fastmail.com>
Message-ID: <DEA2E5D2-0161-4185-A02B-31C3C57D1627@rwec.co.uk>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 23 January 2026 16:05:28 GMT, Larry Garfield <larry@garfieldtech=2Ecom> =
wrote:
>3=2E Unlike the other commenters, I am 100% in favor of allowing `string`=
 to accept Stringable in strict mode=2E  Strict mode basically broke String=
able, and that's been an annoyance for a long time=2E  I know some feel tha=
t Stringable is always and forever a bad thing, amen, but I don't agree=2E =
 It has ample valid use cases, even if it can be abused=2E  I want my Strin=
gable objects back! :-)

I genuinely don't understand the reasoning here=2E If you want type coerci=
on, why are you running in strict_types=3D1 mode? Why would you want to all=
ow objects to be coerced, but not other values with unique, well-defined, s=
tring representations, like integers?

Also, what do you mean by "strict mode broke Stringable"? Do you mean ther=
e was some code you wrote in PHP 5 that relied on implicit object-to-string=
 conversion? It certainly wasn't called "Stringable" at the time; and it wo=
uld have to have been internal functions, because users couldn't define "st=
ring" parameters=2E


Rowan Tommins
[IMSoP]