[PHP-DEV] [RFC] [VOTE] Random Extension 5.x

2022-06-13 Thread Go Kudo
Hello internals. Voting began on 2022-06-14 00:00:00 (UTC) and will end on 2022-06-28 00:00:00 (UTC). https://wiki.php.net/rfc/rng_extension The implementation is not yet complete and has some issues. See TODO in Pull Request for details. https://github.com/php/php-src/pull/8094 Best Regards,

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Dan Ackroyd
Hi Larry, Arnaud, On Mon, 13 Jun 2022 at 13:57, Arnaud Le Blanc wrote: > > Auto-capture in PHP is by-value. This makes this impossible. It also makes > explicit declarations non-necessary and much less useful. > Separating off some pedantism from the hopefully constructive comment, I think

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Rowan Tommins
On 13/06/2022 14:52, Larry Garfield wrote: That's one perspective. The other perspective is that the proposal is to extend closure syntax to support automatic capture. As noted before, this is a distinction without a difference. It's a difference in focus which is very evident in some of the

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Dan Ackroyd
Hi Arnaud, Arnaud Le Blanc wrote: > > Following your comment, I have clarified a few things in the "Auto-capture > semantics" section. This includes a list of way in which these effects can be > observed. These are really marginal cases that are not relevant for most > programs. Cool, thanks.

[PHP-DEV] Re: [RFC] [Vote] Pre-vote announcement for Random Extension 5.x

2022-06-13 Thread Go Kudo
2022年5月31日(火) 18:54 Go Kudo : > Hi internals. > > Although I have explained that due to the global turmoil I will delay > voting on the RFC as long as possible, it is time to start voting on the > RFC in order to get the implementation to full status by the PHP 8.2 > Feature Freeze. > > I

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Larry Garfield
On Mon, Jun 13, 2022, at 8:36 AM, Rowan Tommins wrote: > On 13/06/2022 13:57, Arnaud Le Blanc wrote: >> The proposal is to extend the Arrow Functions syntax so that it allows >> multiple statements. > > > That's one perspective. The other perspective is that the proposal is to > extend closure

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Rowan Tommins
On 13/06/2022 13:57, Arnaud Le Blanc wrote: The proposal is to extend the Arrow Functions syntax so that it allows multiple statements. That's one perspective. The other perspective is that the proposal is to extend closure syntax to support automatic capture. Currently the `use()`

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Rowan Tommins
On 13/06/2022 13:29, Arnaud Le Blanc wrote: Following your comment, I have clarified a few things in the "Auto-capture semantics" section. This includes a list of way in which these effects can be observed. These are really marginal cases that are not relevant for most programs. I'm not sure

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Arnaud Le Blanc
On samedi 11 juin 2022 23:14:28 CEST Rowan Tommins wrote: > My main concern is summed up accidentally by your choice of subject line > for this thread: is the proposal to add *short closure syntax* or is it > to add *auto-capturing closures*? The proposal is to extend the Arrow Functions syntax

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Arnaud Le Blanc
On dimanche 12 juin 2022 20:05:02 CEST Dan Ackroyd wrote: > On Thu, 9 Jun 2022 at 17:34, Larry Garfield wrote: > > That RFC didn't fully go to completion due to concerns over the > > performance impact > I don't believe that is an accurate summary. There were subtle issues > in the previous RFC

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Arnaud Le Blanc
On lundi 13 juin 2022 12:28:17 CEST Robert Landers wrote: > From a maintainer and code review aspect, I prefer the longer syntax > because it is 100% clear on which variables are being closed over and > utilized in the anonymous function. fn($x) => $x + $y is pretty clear > that $y is being pulled

Re: [PHP-DEV] [VOTE] [RFC] Expand deprecation notice scope for partially supported callables

2022-06-13 Thread Juliette Reinders Folmer
L.S., I have opened the vote on the "Expand deprecation notice scope for partially supported callables" RFC: https://wiki.php.net/rfc/partially-supported-callables-expand-deprecation-notices The vote will run for two weeks and will close on June 14, 10:30 UTC. The discussion threads about

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Robert Landers
On Mon, Jun 13, 2022 at 11:36 AM Arnaud Le Blanc wrote: > > On dimanche 12 juin 2022 19:54:06 CEST Mark Baker wrote: > > Did many of those closures use "pass by reference" in the use clause, > > because that's one real differentiator between traditional closures and > > short lambdas. There's

Re: [PHP-DEV] [RFC] [Vote] Pre-vote announcement for Random Extension 5.x

2022-06-13 Thread Go Kudo
2022年6月13日(月) 16:14 Tim Düsterhus : > Hi > > On 6/13/22 04:23, Go Kudo wrote: > > I have created a PoC that allows all internal operations to be performed > in > > 64-bit environments to achieve the same results, although the efficiency > of > > execution in 32-bit environments will be reduced.

Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3

2022-06-13 Thread Arnaud Le Blanc
On dimanche 12 juin 2022 19:54:06 CEST Mark Baker wrote: > Did many of those closures use "pass by reference" in the use clause, > because that's one real differentiator between traditional closures and > short lambdas. There's also the fact that use values are bound at the > point where the

Re: [PHP-DEV] [RFC] [Vote] Pre-vote announcement for Random Extension 5.x

2022-06-13 Thread Tim Düsterhus
Hi On 6/13/22 04:23, Go Kudo wrote: I have created a PoC that allows all internal operations to be performed in 64-bit environments to achieve the same results, although the efficiency of execution in 32-bit environments will be reduced. (Note that Randomizer::getInt() with no argument is still