Re: [PHP-DEV] RFC: First Class Callables in constant expressions

2025-01-31 Thread Larry Garfield
On Fri, Jan 31, 2025, at 5:03 AM, Tim Düsterhus wrote: > Hi > > Am 2025-01-31 00:58, schrieb Larry Garfield: >> I don't know how to interpret the radio silence from the list, but this >> seems like an obvious and good follow-on to the previous RFC and has my >> support. > > We also interpreted th

Re: [PHP-DEV] RFC Karma Request

2025-01-31 Thread Ilija Tovilo
Hi Dmitrii On Fri, Jan 31, 2025 at 3:10 PM Dmitry Derepko wrote: > > I’m looking for way to gain some Karma to create an RFC. > I’ve already made first implementation and shared it: > https://github.com/php/php-src/pull/17647 > > I can make 3 different RFC to discuss each change separately, let

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Arkadiy Kulev
Posted to Github: https://github.com/php/php-src/issues/17661 >

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Jakub Zelenka
On Fri, Jan 31, 2025 at 4:06 PM Arkadiy Kulev wrote: > Hi! > > >> This wouldn't really work because FPM does not control the script during execution and would have to check it out after each allocation which is not really viable. >>> >>> Thanks for the feedback! I agree that m

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Arkadiy Kulev
Hi! > This wouldn't really work because FPM does not control the script during >>> execution and would have to check it out after each allocation which is not >>> really viable. >>> >> >>> >> Thanks for the feedback! I agree that monitoring memory usage after each >> allocation would be infeasibl

[PHP-DEV] RFC Karma Request

2025-01-31 Thread Dmitry Derepko
Hi! I’m looking for way to gain some Karma to create an RFC. I’ve already made first implementation and shared it: https://github.com/php/php-src/pull/17647 I can make 3 different RFC to discuss each change separately, let me know if it’s necessary. -- Best regards, Dmitrii Derepko.

Re: [PHP-DEV] RFC: Marking return values as important (#[\NoDiscard])

2025-01-31 Thread Tim Düsterhus
Hi Am 2025-01-30 18:48, schrieb Claude Pache: BTW, the RFC says that introducing the `(void)` cast is a backward compatible change, which is incorrect; see: https://3v4l.org/iN7OY :-| Thank you for pointing that out. We've adjusted the “Backward Incompatible Changes” section accordingly and

Re: [PHP-DEV] RFC: First Class Callables in constant expressions

2025-01-31 Thread Tim Düsterhus
Hi Am 2025-01-31 00:58, schrieb Larry Garfield: I don't know how to interpret the radio silence from the list, but this seems like an obvious and good follow-on to the previous RFC and has my support. We also interpreted the lack of responses as “this is an obvious follow-up and I don't have

Re: [PHP-DEV] RFC: First Class Callables in constant expressions

2025-01-31 Thread Arvids Godjuks
On Fri, 31 Jan 2025 at 01:59, Larry Garfield wrote: > On Wed, Jan 22, 2025, at 8:35 AM, Tim Düsterhus wrote: > > Hi > > > > Volker and I would like to start discussion on our RFC to support "First > > Class Callables in constant expressions". > > > > Please find the following resources for your r

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Jakub Zelenka
> > > To be honest, I haven't seen a 'slow' memory leak in a long time -- except > when using fgetcsv which has had a reported memory leak since ~2012 > somewhere on the old bug tracker. (I lost the link to it and don't even > remember how to get to the tracker or if it still exists.) I haven't > c

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Jakub Zelenka
Hi, > This wouldn't really work because FPM does not control the script during >> execution and would have to check it out after each allocation which is not >> really viable. >> > > Thanks for the feedback! I agree that monitoring memory usage after each > allocation would be infeasible. However