Re: [PHP-DEV] [RFC][Under discussion] Fetch properties in const expressions

2022-06-14 Thread shinji igarashi
Hello! Just a question. Would this also be allowed? https://3v4l.org/RGdIA i; const ClassConstantViaPropertyFetching2 = B::ClassConstant->i; } Thanks! -- Shinji Igarashi 2022年5月28日(土) 18:44 Ilija Tovilo : > > Hi everyone > > I'd like to start a discussion on a simple RFC to allow

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

2022-06-14 Thread Björn Larsson via internals
Den 2022-06-13 kl. 14:57, skrev 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

Re: [PHP-DEV] [RFC][Under discussion] Fetch properties in const expressions

2022-06-14 Thread Ilija Tovilo
Hi Robert, hi Guilliam > > So, how does this change our mental models when writing PHP? For > > example, I generally consider `const` to be a "compile-time" constant > > (ie, generated/created before any code is actually executed). So would > > this allow code to actually execute before any other

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

2022-06-14 Thread Rowan Tommins
(Sorry for double reply, hit send too soon) On 14/06/2022 12:18, Arnaud Le Blanc wrote: Your example uses isset(), which is valid code in most circumstances, but as you said it's not particularly good code. Do you have other examples that come to mind ? There is plenty of code out there in

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

2022-06-14 Thread Rowan Tommins
On 14/06/2022 12:18, Arnaud Le Blanc wrote: - The closure mutates a value accessed through a captured variable. Mutable values include objects and resources, but NOT scalars or arrays (since they are copy-on-write). It's not something that is used very often, so is often forgotten or

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

2022-06-14 Thread Mike Schinkel
> On Jun 13, 2022, at 1:39 PM, Rowan Tommins wrote: > > 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

Re: [PHP-DEV] The future of objects and operators

2022-06-14 Thread Robert Landers
On Fri, May 13, 2022 at 4:49 PM Jordan LeDoux wrote: > > On Fri, May 13, 2022 at 7:05 AM Rowan Tommins > wrote: > > > > > I like Larry's "4 levels", but I've been thinking that there's some > > existing functionality in PHP which takes a different direction: rather > > than overloading

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

2022-06-14 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-14 Thread Arnaud Le Blanc
On lundi 13 juin 2022 15:36:26 CEST Rowan Tommins wrote: > > Auto-capture in PHP is by-value. This makes this impossible. It also makes > > explicit declarations non-necessary and much less useful. > > > > Live-variable analysis is mentioned in as part of implementation details. > > It should not

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

2022-06-14 Thread Arnaud Le Blanc
Hi Dan, On lundi 13 juin 2022 19:49:10 CEST Dan Ackroyd 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 some