Hello! I have one concern about the part:
> Emit an E_WARNING when $start or $end is cast to an integer because the other boundary input is a number or numeric string. (e.g. range <http://www.php.net/range>('5', 'z'); or range <http://www.php.net/range>(5, 'z');) Doesn't it limit the functionality of the function for the numbers as characters? Currently when we call range('/','z') we get full range of characters. https://onlinephp.io/c/9cb12 But when we change argument $start to next character which is zero ('0') then we get array with only one element. https://onlinephp.io/c/a0cda Casting numerical string in this function may be confusing. Sorry for making fuss just before voting, but didn't see this topic before and wanted to share my insights with you thinking it may be relevant. Kind regards, Jorg On Mon, May 15, 2023 at 4:42 PM G. P. B. <george.bany...@gmail.com> wrote: > Hello Internals, > > I plan to put the RFC to a vote tomorrow in its current state, which has > not been changed since the 30th of March: > https://wiki.php.net/rfc/proper-range-semantics > > Any final comments or complaints should be raised now. > > Best regards, > > George P. Banyard >
