Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129893
Message-ID: <31563ed1-ac44-47ef-9fca-3ebbfc567ba5@sandfox.me>
Date: Fri, 23 Jan 2026 16:55:58 +0200
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Deprecate Fuzzy Type Casts and Allow Stringable
 in Strict Mode
To: internals@lists.php.net
References: <CAMU7ir+1VfQCiSVG0BjN5V+upNU2kU+a_rKDXO1=Ahu3ndmOGg@mail.gmail.com>
 <CANS-=pfCasTNSAMSdL8ajJMnrwNpfvbEOoQTQhAQ=X73iG+_tw@mail.gmail.com>
 <CAMU7irLgsMCzHsQDD6Ok2zJZsNyV7LF-PHotzqvSGRAkN9bovg@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAMU7irLgsMCzHsQDD6Ok2zJZsNyV7LF-PHotzqvSGRAkN9bovg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: sandfox@sandfox.me (Anton Smirnov)

On 23/01/2026 16:17, Alexandre Daubois wrote:
> I understand the concern about legacy code. However, if code relies on
> `(int) "123abc"` silently returning `123`, this represents a data
> integrity issue that would benefit from being made explicit. The
> deprecation period exists specifically to help identify and address
> these cases.

Hi, Alexandre

While I agree that this code likely indicates some form of broken logic, 
this code still needs a clear migration path, so introducing something 
like fuzzy_int() function with the old behavior I'd say is expected.

Second, there should be a time frame where an old and a new way can 
coexist so deprecating it in 8.x feels a bit rushed. To me a perfect 
migration would be something like

8.6: introduce fuzzy_int or even a family of functions (fuzzy_float?)
9.1: deprecate
10.0: TypeError

-- 
Anton