Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113371
MIME-Version: 1.0
Date: Thu, 4 Mar 2021 13:07:25 +0000
Message-ID: <CAFPFaMJJrOvVQn4K-34ApqFy83Ge4wZ79QwvcQaZkavEdr4Lbg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c6077b05bcb5a64e"
Subject: [PHP-DEV] [RFC] Deprecate implicit non-integer-compatible float to
 int conversions
From: george.banyard@gmail.com ("G. P. B.")

--000000000000c6077b05bcb5a64e
Content-Type: text/plain; charset="UTF-8"

Hello internals,

This is a follow-up on the previous thread [1] about my RFC tackling
implicit float to int conversion.
It is now slightly larger in scope as it also pertains to what I call "non
compatible integer floating numbers".

This new version of the RFC can be found on the wiki: [2]
https://wiki.php.net/rfc/implicit-float-int-deprecate

Feedback is as usual welcomed, however I am not interested in changing the
behaviour of explicit casts.
One detail is if this RFC should also allow the usage of int compatible
float strings for string offsets, behaviour which has been removed in PHP
8.0 with the Saner Numeric Strings RFC. [3]

Best regards,

George P. Banyard

[1] "[RFC] Warning for implicit float to int conversions"
https://externals.io/message/113077
[2] https://wiki.php.net/rfc/implicit-float-int-deprecate
[3] https://wiki.php.net/rfc/saner-numeric-strings

--000000000000c6077b05bcb5a64e--