wt., 21 lip 2020 o 07:07 tyson andre napisał(a):
> > Can you give an example of an internal stack frame?
>
> A stack frame that was created by a PHP internal function instead of by
> userland code, i.e. one without a file in the frame.
> Related to
> https://github.com/php/php-src/pull/5820#pullr
> Can you give an example of an internal stack frame?
A stack frame that was created by a PHP internal function instead of by
userland code, i.e. one without a file in the frame.
Related to https://github.com/php/php-src/pull/5820#pullrequestreview-452080212
```
php > array_map(fn() => $GLOBAL
Hi Tyson,
wt., 21 lip 2020 o 06:54 tyson andre napisał(a):
> Hi Michał Marcin Brzuchalski,
>
> At the time of writing, the documentation in
> https://wiki.php.net/rfc/stack-frame-class#stackframe_class is also
> inconsistent with the implementation.
> `public readonly string $file;` is not actua
Hi Tyson,
wt., 21 lip 2020 o 04:27 tyson andre napisał(a):
> ...
> I had some comments on the implementation in
> https://github.com/php/php-src/pull/5820#pullrequestreview-452045885
>
Most of these comments can be worked upon the next days in the meantime.
> - How much does this change elaps
Hi Michał Marcin Brzuchalski,
At the time of writing, the documentation in
https://wiki.php.net/rfc/stack-frame-class#stackframe_class is also
inconsistent with the implementation.
`public readonly string $file;` is not actually read only in the implementation
in the GitHub PR. It can be overwr
Hi Michał Marcin Brzuchalski,
> Heads up, I plan to open the vote tomorrow morning.
Sorry for the late comment - I'd been busy/occupied with various other things
and this RFC fell off my radar,
and I'd assumed that anything I'd end up noticing when looking at the RFC
would have already been po
On 20/07/2020 16:58, Michael Wallner wrote:
Distilled down, I just cannot see any huge benefit out of a (or two) root
namespace(s). As a project we rightfully own the root namespace, and
putting everything beneath PHP just doesn't make any sense to me.
You cannot just "own" the root namespace i
Hi Internals,
Heads up, I plan to open the vote tomorrow morning.
Cheers,
Michał Marcin Brzuchalski
wt., 7 lip 2020 o 22:46 Michał Marcin Brzuchalski <
michal.brzuchal...@gmail.com> napisał(a):
> Hi internals,
>
> following recently added alternative to `token_get_all()` in form of a
> dedicate
On Fri, 10 Jul 2020 at 09:42, Nikita Popov wrote:
> Hi internals,
>
> I have opened voting on the named arguments RFC:
> https://wiki.php.net/rfc/named_params
>
I see this vote is currently running close to the super-majority threshold.
To those of you whose main concern is the need for libra
On Mon, 20 Jul 2020 at 16:58, Michael Wallner wrote:
> Distilled down, I just cannot see any huge benefit out of a (or two) root
> namespace(s). As a project we rightfully own the root namespace, and
> putting everything beneath PHP just doesn't make any sense to me.
>
I will ask you the same q
Hi Larry!
Larry Garfield schrieb am Mi., 24. Juni 2020,
02:30:
> Greetings, Internalians.
>
> *dons flame retardant suit*
Thank your for your efforts, but I'm about to cast a negative vote on this
policy.
Distilled down, I just cannot see any huge benefit out of a (or two) root
namespace(s).
On Mon, Jul 13, 2020 at 11:37 AM Levi Morrison wrote:
>
> Hello everyone,
>
> I'd like to change the default mode of assertion failures to throw.
> The current default is to warn. In my opinion this is a bad strategy:
> the engine asserted that something that is expected to be true is not,
> so ex
12 matches
Mail list logo