Greetings, Internalians.
There has been much talk of the \PHP namespace of late, including one
unsuccessful RFC. In the discussion, the pushback broke down into two main
camps:
* We should never namespace anything ever.
* We can namespace things but we need something more concrete than "RFCs
> Le 16 juin 2020 à 10:52, Nikita Popov a écrit :
>
> Hi internals,
>
> Inspired by the recent discussion on reserved keyword reservation, I'd like
> to propose the following RFC:
>
> https://wiki.php.net/rfc/namespaced_names_as_token
>
> This RFC makes two related changes: Treat namespaced
On Tue, 23 Jun 2020 at 09:54, Björn Larsson
wrote:
>
> Ok, thanks for the clarification. The reason for me to bring
> this up is that I was pondering on if this is the only place in
> PHP where a semicolon is required after a curly bracket
> when not used in an expression.
>
Two things:
- as
On Tue, May 5, 2020 at 3:51 PM Nikita Popov wrote:
> Hi internals,
>
> I've recently started a thread on resurrecting the named arguments
> proposal (https://externals.io/message/109549), as this has come up
> tangentially in some recent discussions around attributes and around object
>
Maintaining an official, bundled PHP extension
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Den 2020-06-23 kl. 10:30, skrev Ilija Tovilo:
Hi Björn
I'd like to announce the match expression v2 RFC:
https://wiki.php.net/rfc/match_expression_v2
Absolutely so. I was thinking of the case mentioned in v1 RFC when it's used
as a stand-alone expression.
match ($y) {
...
};
` Optional?
Hey,
On Tue, Jun 23, 2020, 11:34 AM Ilija Tovilo wrote:
> Hi Benas
>
> >> I'd like to announce the match expression v2 RFC:
> >> https://wiki.php.net/rfc/match_expression_v2
>
> > Then it's not a standalone expression but a block. In this case, you
> cannot add an optional semicolon at all.
> >
Hi Benas
>> I'd like to announce the match expression v2 RFC:
>> https://wiki.php.net/rfc/match_expression_v2
> Then it's not a standalone expression but a block. In this case, you cannot
> add an optional semicolon at all.
>
> But this RFC v2 is not proposing to add a block, therefore you
On Tue, Jun 23, 2020, 11:23 AM Björn Larsson
wrote:
> Den 2020-06-22 kl. 18:05, skrev Benas IML:
>
> > On Mon, Jun 22, 2020, 6:35 PM Björn Larsson
> > wrote:
> >
> >> Hi Ilija,Den 2020-06-18 kl. 22:51, skrev Ilija Tovilo:
> >>
> >>> Hi Björn
> >>>
> > I'd like to announce the match
Hi Björn
>> I'd like to announce the match expression v2 RFC:
>> https://wiki.php.net/rfc/match_expression_v2
> Absolutely so. I was thinking of the case mentioned in v1 RFC when it's used
> as a stand-alone expression.
> match ($y) {
> ...
> };
> ` Optional?
In this RFC the semicolon is
Den 2020-06-22 kl. 18:05, skrev Benas IML:
On Mon, Jun 22, 2020, 6:35 PM Björn Larsson
wrote:
Hi Ilija,Den 2020-06-18 kl. 22:51, skrev Ilija Tovilo:
Hi Björn
I'd like to announce the match expression v2 RFC:
https://wiki.php.net/rfc/match_expression_v2
Well one could argue that when
11 matches
Mail list logo
