Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129898
Feedback-ID: i8414410d:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Fri, 23 Jan 2026 10:05:28 -0600
To: "php internals" <internals@lists.php.net>
Message-ID: <53f11b44-11c1-4b23-a8be-c7846262a49c@app.fastmail.com>
In-Reply-To: 
 <CAMU7ir+1VfQCiSVG0BjN5V+upNU2kU+a_rKDXO1=Ahu3ndmOGg@mail.gmail.com>
References: 
 <CAMU7ir+1VfQCiSVG0BjN5V+upNU2kU+a_rKDXO1=Ahu3ndmOGg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Deprecate Fuzzy Type Casts and Allow Stringable in Strict
 Mode
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Fri, Jan 23, 2026, at 4:48 AM, Alexandre Daubois wrote:
> Hello everyone,
>
> Before going further with our already under discussion RFC about
> nullable casts, Nicolas Grekas and I would like to present this new
> RFC about deprecating fuzzy casts, and adding support for Stringable
> in string parameters when using strict mode.
>
> RFC: https://wiki.php.net/rfc/deprecate-fuzzy-casts
>
> Thanks,
>
> =E2=80=94 Alexandre Daubois

1. This really feels like two separate RFCs.  I'd rather see them as two=
 separate RFCs than one mixed RFC.

2. I tend to agree with other commenters that we should leave the existi=
ng casts alone, and instead add a new, more reasonable type conversion o=
perators (for some definition of reasonable). =20

3. Unlike the other commenters, I am 100% in favor of allowing `string` =
to accept Stringable in strict mode.  Strict mode basically broke String=
able, and that's been an annoyance for a long time.  I know some feel th=
at Stringable is always and forever a bad thing, amen, but I don't agree=
.  It has ample valid use cases, even if it can be abused.  I want my St=
ringable objects back! :-)

--Larry Garfield