Hi,
This is fine to me.
I stopped active JIT development, and going to do only fixes and may be
minor improvements.
Thanks. Dmitry.
On Mon, Sep 28, 2020 at 11:56 AM Gabriel Caruso
wrote:
> Following Sara's email a couple of weeks ago, I come this week with a
> similar one:
>
> Next Tuesday, Se
On Mon, Sep 28, 2020 at 10:56 AM Gabriel Caruso
wrote:
> Following Sara's email a couple of weeks ago, I come this week with a
> similar one:
>
> Next Tuesday, Sep 29th, has been marked on our calendars as the branch date
> for PHP-8.0 which would open master up for 8.1 targeted work.
>
> This wo
On Mon, Sep 28, 2020 at 4:35 PM Benjamin Morel
wrote:
> On Mon, 28 Sep 2020 at 15:17, Nicolas Grekas
> wrote:
>
>> I assume the 80% case is properties, because attributes did not have
>>> docblock annotations yet, that means this use-case isn't even possible at
>>> the moment. Yet annotations on
On Mon, 28 Sep 2020 at 15:17, Nicolas Grekas
wrote:
> I assume the 80% case is properties, because attributes did not have
>> docblock annotations yet, that means this use-case isn't even possible at
>> the moment. Yet annotations on properties are widespread (Doctrine ORM,
>> symfony validator,
>
> >> imho, we should pick the 80% use-case and advise to desugar the code if
> >> other behavior is desired. For me the 80% case is that the attribute
> only
> >> applies to the property, not to the parameter.
> >
> >
> > +1 for the desugaring advice in this case, however as a matter of
> > consi
On Mon, Sep 28, 2020 at 2:25 PM Benjamin Morel
wrote:
> On Mon, 28 Sep 2020 at 13:56, Benjamin Eberlei
> wrote:
>
>
>> imho, we should pick the 80% use-case and advise to desugar the code if
>> other behavior is desired. For me the 80% case is that the attribute only
>> applies to the property
> Hi Benjamin, hi everyone
>>
>> I'm wondering if the syntax that allows for several attributes is really
>> future-proof when considering nested attributes:
>>
>>
>> *1.*
>> #[foo]
>> #[bar]
>>
>> VS
>>
>>
>> *2.*
>> #[foo, bar]
>>
>> Add nested attributes to the mix, here are two possible ways:
>
On Mon, 28 Sep 2020 at 13:56, Benjamin Eberlei
wrote:
> imho, we should pick the 80% use-case and advise to desugar the code if
> other behavior is desired. For me the 80% case is that the attribute only
> applies to the property, not to the parameter.
+1 for the desugaring advice in this ca
On Mon, Sep 28, 2020 at 12:36 PM Nikita Popov wrote:
> Hi internals,
>
> When the constructor property promotion landed, the question of how it
> interacts with attributes on promoted properties did not get fully
> resolved. See https://wiki.php.net/rfc/constructor_promotion#attributes
> for what
Hi internals,
When the constructor property promotion landed, the question of how it
interacts with attributes on promoted properties did not get fully
resolved. See https://wiki.php.net/rfc/constructor_promotion#attributes for
what the issue is.
The behavior that landed was to apply the attribut
On Sun, Sep 27, 2020 at 10:23 AM Nicolas Grekas
wrote:
> Hi Benjamin, hi everyone
>
> I'm wondering if the syntax that allows for several attributes is really
> future-proof when considering nested attributes:
>
>
> *1.*
> #[foo]
> #[bar]
>
> VS
>
>
> *2.*
> #[foo, bar]
>
> Add nested attributes
Following Sara's email a couple of weeks ago, I come this week with a
similar one:
Next Tuesday, Sep 29th, has been marked on our calendars as the branch date
for PHP-8.0 which would open master up for 8.1 targeted work.
This would mean that bug fixes would need to include PHP-8.0 in their merge
12 matches
Mail list logo
