Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128582
Precedence: list
MIME-Version: 1.0
Date: Thu, 28 Aug 2025 13:28:43 +0200
To: Morgan <Weedpacket@varteg.nz>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add clamp function
In-Reply-To: <32e94a0f-2e2b-48f3-90a0-ad0096608809@varteg.nz>
References: <CADyq6sKVyL=Ck_OeBwe+EQH1Lz0s_X1Qf3yM4H6cQg3sykMN_g@mail.gmail.com>
 <1756361767126.3727989781.4204927711@yahoo.de>
 <3b1bd29cd42074b499d38e10cb97bf42@bastelstu.be>
 <32e94a0f-2e2b-48f3-90a0-ad0096608809@varteg.nz>
Message-ID: <f25b801a36c86b37e79e16ee42b14a63@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

>> There's precedent in ext/random with the Randomizer::getFloat() method 
>> that takes a Random\IntervalBoundary enum to decide on the the 
>> interpretation of the boundary values. Translated to `clamp()` this 
>> could mean:
>> 
> If it weren't living in the Random extension, that very Enum could have 
> been used.

Indeed. Back when introducing the enum, we actually had a discussion 
about naming and “placement”. In the end, we opted to make it 
ext/random-specific as a more conservative choice. I think back then it 
was the first native enum.

See https://externals.io/message/118810#118910 and 
https://chat.stackoverflow.com/transcript/11?m=55444127#55444127.

If a new general-purpose IntervalBoundary enum is introduced, I'm happy 
to widen the type in ext/random from `\Random\IntervalBoundary` to 
`\IntervalBoundary|\Random\IntervalBoundary` (and deprecate the latter 
in one of the following versions).

Best regards
Tim Düsterhus