Hi Theodore,
śr., 29 lip 2020 o 21:08 Theodore Brown napisał(a):
> ...
> Anyway, apart from the fact that feature freeze is less than a week
> away, it seems like voting again to use #[] instead of @@ would
> violate the voting rules. [1] It hasn't been six months since the
> last vote, and this
On Tue, July 28, 2020 at 6:09 PM Mark Randall wrote:
> On 28/07/2020 22:55, Theodore Brown wrote:
> > I appreciate the examples. I think there are good reasons not to
> > implement these kind of extensions, at least in this form. I'll reply
> > to each example below.
>
>
> The problem is your a
Hi Joe,
wt., 28 lip 2020 o 16:47 Joe Ferguson napisał(a):
> Hello Internals,
>
> I've been working with Derick Rethans and others (thanks all!) on a Shorter
> Attribute Syntax Change RFC which outlines reasons why the "#[]" syntax
> would be preferred over the currently agreed upon "@@" syntax f
Hi internals,
> Voting on https://wiki.php.net/rfc/trailing_comma_in_closure_use_list has
> started, and ends on 2020-07-29.
>
> This proposes allowing a single optional trailing comma in closure use lists.
https://wiki.php.net/rfc/trailing_comma_in_closure_use_list has been accepted
and merged
Oh, you are right! "yield from" is not common for me currently, so I really
skipped it.
In this case, is there some problem to apply it to Attribute case? "using
attribute(Attribute())" or something like that?
Atenciosamente,
David Rodrigues
Em qua., 29 de jul. de 2020 às 14:01, Nikita Popov
On Wed, Jul 29, 2020 at 6:50 PM David Rodrigues
wrote:
> Hello!
>
> I do not know if there is some consensus about "why not use two words as a
> single keyword" in programming language in general, but I really found a
> few examples of it, as in SQL with "GROUP BY", for instance.
>
> So I questio
Hello!
I do not know if there is some consensus about "why not use two words as a
single keyword" in programming language in general, but I really found a
few examples of it, as in SQL with "GROUP BY", for instance.
So I question if it could be used on PHP to expand the keywords repertoire
by mix
Hi internals,
I had thought of another alternative syntax - `/** @@MyAttribute */`, which
would solve some of the problems I mentioned about `#[`.
```
namespace My\NS;
use Other\MyAttribute;
/**
* Use @@ or << at the start of a line. (To be determined)
* Resolve the names in the comment relati
Hi Michal,
> On Jul 29, 2020, at 01:13, Michał Marcin Brzuchalski
> wrote:
>
> Hi Paul,
>
> wt., 28 lip 2020 o 20:56 Paul M. Jones napisał(a):
>
>> ...
>> Let's count. + is "change away from @@ to anything else", - is "stay with
>> @@", ? is hard-to-tell/weak/uncertain/they-all-suck.
>> ...
Hello Internals,
Here is a small comparison table based on current feedback, maybe it
will bring some objective clarity to the discussion:
(markdown below)
Impact|`@@`|`#[]`
---|---|---
BC break|virtualy nonexistent|slightly broader: `##[` comments are now broken.
Parser|no technical problems by
On Wed, 29 Jul 2020 at 03:31, Ryan Jentzsch wrote:
> https://phil.tech/2013/wtf-is-t-paamayim-nekudotayim/
https://3v4l.org/guXbl#v800alpha3
You're welcome.
--
Rowan Tommins
[IMSoP]
On Wed, Jul 29, 2020 at 2:21 AM tyson andre
wrote:
> Hi internals,
>
> For #[, my main objection is the various ways this can change the lexing
> in a way that is impractical to (efficiently) backfill,
> and that the proposed patch doesn't address the fact that the syntax may
> change the syntax
12 matches
Mail list logo
