On Thu, Jun 30, 2022 at 7:37 PM Arnaud Le Blanc wrote:
>
> On jeudi 30 juin 2022 18:29:44 CEST Guilliam Xavier wrote:
> > Ah? Sorry, I had interpreted
> > https://github.com/php/php-src/pull/8330/files#diff-85701127596aca0e597bd796
> > 1b5d59cdde4f6bb3e2a109a22be859ab7568b4d2R7318-R7320 as "captur
On Thu, 30 Jun 2022 at 23:21, Levi Morrison via internals <
internals@lists.php.net> wrote:
> On Thu, Jun 30, 2022 at 10:48 AM Pierrick Charron
> wrote:
> > One of the goal of this API is to tighten a problematic vulnerable area
> > for applications where the URL parser library would believe one
Hi
On 7/1/22 12:07, Rowan Tommins wrote:
My concern is rather the opposite: if it is not obvious *to someone writing
PHP code* how the API should be used, there is a higher chance of them
using it incorrectly, and introducing errors.
A good example of this mindset is the password_* functions: t
Hi Guilliam,
Thank you for noticing.
The PR is now fully in sync with the RFC (no arrow function changes, no
explicit use support).
The RFC also now clarifies that arrow functions are not changed by the RFC.
Hi Rowan,
Since this still has a small chance of breaking existing code, we preferred
to exclude arrow functions from this change, for now. We have added this in
Future Scope. This is something we could do in a follow-up RFC.
Regards,
Hi Björn,
On Wed, Jun 29, 2022 at 8:09 PM Björn Larsson via internals <
internals@lists.php.net> wrote:
> Would it be an option to include a "Future scope" with the features:
> - Explicit capture that list only the variables to be captured by value
> or reference, nothing else.
> - Extending the
Hi everyone
I opened voting for the "Fetch properties of enums in const expressions" RFC.
https://wiki.php.net/rfc/fetch_property_in_const_expressions
Voting closes on 2022-07-15.
Ilija
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Greetings, Internalians.
The vote for auto-capture closures is now open. It will run until 15 July.
https://wiki.php.net/rfc/auto-capture-closure
--
Larry Garfield
la...@garfieldtech.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/un
>As far as we are aware, only two languages in widespread use require
variables to be explicitly closed over: PHP and C++. All other major
languages capture implicitly, as is proposed here.
to be fair to c++, it supports [&] to capture everything, like
int a=1,b=2,c=3;[&]()->void{std::cout << a <<
On Fri, 1 Jul 2022 at 15:05, Larry Garfield wrote:
>
> The vote for auto-capture closures is now open. It will run until 15 July.
Voting no as:
i) changes in the implementation need more than 1.5 hours discussion
between that change and the voting opening.
ii) The inconsistency of capturing ru
2022年6月29日(水) 17:40 Guilliam Xavier :
> >> > https://wiki.php.net/rfc/random_extension_improvement
> >>
> >> I just realized a little thing: in the array_rand() example, for
> >> $beforeSingle, it would probably be "more realistic" to omit `, 1`
> >> (which is already the default for $num).
> >>
>
Hello, everyone!
I have updated the RFC for constants in traits to reflect the discussion at
ML and answer some additional questions, as well as add sections on
comparisons to other languages and future scope, and modify some
sentences for clarity.
https://wiki.php.net/rfc/constants_in_traits
If
On Fri, 2022-07-01 at 16:11 +0200, Hans Henrik Bergan wrote:
> > As far as we are aware, only two languages in widespread use
> > require variables to be explicitly closed over: PHP and C++. All
> > other major languages capture implicitly, as is proposed here.
But do any of them auto-capture by v
13 matches
Mail list logo
