Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128314
Precedence: bulk
MIME-Version: 1.0
References: <CAMU7irKj_SyyM2kVz4kEqjDK+ucc8uRP1amJgASTFRM+V+Ld3w@mail.gmail.com>
 <1785545681.303988.1753812863978@email.ionos.de>
In-Reply-To: <1785545681.303988.1753812863978@email.ionos.de>
Date: Wed, 30 Jul 2025 08:43:46 +0200
Message-ID: <CAMU7irJw1b6QyM2E8s6JShstcMuTNFjGPbDGyoWCMNRnJiDREQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Add "is_representable_as_float()" and
 "is_representable_as_int()" functions
To: Thomas Bley <mails@thomasbley.de>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: alex.daubois+php@gmail.com (Alexandre Daubois)

> Since frameworks already have things like Strings::is_stringable() and Arr::arrayable(), I'd suggest to use is_floatable(), is_intable() or is_integerable(), etc.
> To me, this would also feel more consistent is is_float(), is_int(), etc.

I get what you mean. Naming is definitely challenging here. However,
with alternatives like "is_floatable()", I'm afraid that it is not
clear enough that there's a potential loss of precision. I would
personally feel that "is_floatable()" would mean "can this be cast to
float?" without further "limitation".

Best,
Alexandre Daubois