[PHP-DEV] Re: [VOTE] Random Extension Improvement

2022-07-05 Thread Go Kudo
2022年7月3日(日) 12:00 Go Kudo : > Hello internals. > > Voting began on 2022-07-02 03:00:00 (UTC) and will end on 2022-07-16 > 03:00:00 (UTC). > > https://wiki.php.net/rfc/random_extension_improvement > > Best Regards, > Go Kudo > Hi. Once again, I apologize for the delay in starting the voting due

[PHP-DEV] [RFC] [VOTE] Constants in traits

2022-07-05 Thread shinji igarashi
Hello internals, I've started the vote for the Constants in Traits RFC: https://wiki.php.net/rfc/constants_in_traits The vote will end on 19. July 2022. Thanks! -- Shinji Igarashi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php

[PHP-DEV] [PHP8.2] Feature freeze in 2 weeks

2022-07-05 Thread Pierrick Charron
Hi internal, This is yet another friendly reminder from your RMs that the PHP 8.2 feature -freeze is in 2 weeks now [1]. All RFC targeting 8.2 should now be in the voting phase to respect the minimal period of 2 weeks. Also it would be appreciated if some of internal devs could start reviewing

Re: [PHP-DEV] [RFC][Vote] Auto-capture closures

2022-07-05 Thread Arnaud Le Blanc
On mardi 5 juillet 2022 09:27:34 CEST Marco Pivetta wrote: > This is fine, but it creates a bidirectional dependency between components > where the dependency graph was previously (in theory) acyclic. > > This will become "someone else's problem"  I don't think that the Optimizer conceptually

[PHP-DEV] [VOTE] [RFC] Make the iterator_*() family accept all iterables

2022-07-05 Thread Tim Düsterhus , WoltLab GmbH
Hi I just opened the vote on: "Make the iterator_*() family accept all iterables" [1] The RFC contains two votes, each of which requires a 2/3 majority. Voting will run 2 weeks until: 2022-07-19 at 14:45 UTC Please find the below resources for your reference: RFC:

Re: [PHP-DEV] [RFC][Vote] New Curl URL API

2022-07-05 Thread Rowan Tommins
On 05/07/2022 00:34, Pierrick Charron wrote: I opened voting for the new Curl URL API as part of PHP8.2. https://wiki.php.net/rfc/curl-url-api All recent discussions show that we are not even close to getting a consensus on how the new CurlUrl OO API should be done. After changing my mind 300

Re: [PHP-DEV] [RFC] Add json_encode indent parameter

2022-07-05 Thread Andreas Heigl
On 05.07.22 11:38, Jakub Zelenka wrote: On Tue, Jul 5, 2022 at 8:37 AM Andreas Heigl wrote: Hey all. On 05.07.22 02:04, Peter Cowburn wrote: On Mon, 4 Jul 2022 at 11:11, Jakub Zelenka wrote: On Mon, Jul 4, 2022 at 8:38 AM Timon de Groot wrote: Hi internals, If the rest also thinks

Re: [PHP-DEV] [RFC] Add json_encode indent parameter

2022-07-05 Thread Jakub Zelenka
On Tue, Jul 5, 2022 at 8:37 AM Andreas Heigl wrote: > Hey all. > > On 05.07.22 02:04, Peter Cowburn wrote: > > On Mon, 4 Jul 2022 at 11:11, Jakub Zelenka wrote: > > > >> On Mon, Jul 4, 2022 at 8:38 AM Timon de Groot > >> wrote: > >> > >>> Hi internals, > >>> > >>> If the rest also thinks the

Re: [PHP-DEV] [RFC] Add json_encode indent parameter

2022-07-05 Thread Marco Pivetta
Hey Timon, On Fri, 13 May 2022 at 15:33, Timon de Groot wrote: > Hi internals, > > Almost a year ago I first proposed my RFC draft to introduce a new > json_encode parameter 'indent'. I have received a lot of feedback on the > change, very insightful. The feedback can be boiled down to: > -

Re: [PHP-DEV] [RFC] Add json_encode indent parameter

2022-07-05 Thread Aleksander Machniak
On 05.07.2022 09:37, Andreas Heigl wrote: What I would have prefered is instead of a the new parameter $indent having a numerical value to have a string value. That would have allowed the following:     json_encode($data, indent: "    "); or     json_encode($data, indent: "\t"); That

Re: [PHP-DEV] [RFC] Add json_encode indent parameter

2022-07-05 Thread Andreas Heigl
Hey all. On 05.07.22 02:04, Peter Cowburn wrote: On Mon, 4 Jul 2022 at 11:11, Jakub Zelenka wrote: On Mon, Jul 4, 2022 at 8:38 AM Timon de Groot wrote: Hi internals, If the rest also thinks the RFC is good to go, I suggest we start a vote coming week. As this is my first RFC, I'm not so

Re: [PHP-DEV] [RFC][Vote] Auto-capture closures

2022-07-05 Thread Marco Pivetta
On Mon, 4 Jul 2022, 19:15 Arnaud Le Blanc, wrote: > > Important to note how `Zend/zend_compile.c` now depends on `Optimizer/`, > > which is a potential design issue. > > The Optimizer was moved to `Zend/Optimizer` earlier so that in the long > term > it could be used by the compiler pipeline

Re: [PHP-DEV] [RFC][Vote] New Curl URL API

2022-07-05 Thread Nicolas Grekas
> Hi internals, > > I opened voting for the new Curl URL API as part of PHP8.2. > > All recent discussions show that we are not even close to getting a > consensus on how the new CurlUrl OO API should be done. After changing my > mind 300 times in the last day, I decided to only propose the

Re: [PHP-DEV] [RFC][Vote] New Curl URL API

2022-07-05 Thread Pierrick Charron
Sorry about that const CURLUPART_USER = UNKNOWN; // what UNKNOWN? > UNKNOWN means that the value here is not relevant for the user to know. But for clarification, the values of those constants will be the exact same values of the same constants in libcurl. "All errors of libcurl will become

Re: [PHP-DEV] [RFC][Vote] New Curl URL API

2022-07-05 Thread Marco Pivetta
Clear "no" from me on this: this is something similar to a PSR-7 URI object, but with a clunky and mutable API. Something like this would/should go to packagist first, to assess adoption there, but I would certainly not use it. On Tue, 5 Jul 2022, 01:34 Pierrick Charron, wrote: > Hi internals,

Re: [PHP-DEV] [RFC][Vote] New Curl URL API

2022-07-05 Thread Aleksander Machniak
On 05.07.2022 01:34, Pierrick Charron wrote: Hi internals, I opened voting for the new Curl URL API as part of PHP8.2. I found some not clear fragments in the RFC. const CURLUPART_USER = UNKNOWN; // what UNKNOWN? "All errors of libcurl will become CurlUrlException." "Setting a part to a