On Fri, Aug 27, 2021 at 11:11 AM Tobias Nyholm
wrote:
>
> But I do agree with you. The process would have been way better if they
> said “no". Or if they clearly and unanimously said “yes” which would remove
> focus on “it feels rushed” and “we can’t because of feature freeze”.
> This is the the
Tobias Nyholm wrote on 8/27/21 13:11:
>>> one way of reading this proposal is that we don’t trust the release
>>> managers to decide what to include and not to include in a release.
>>
>> To be clear, I don't trust release managers to decide that. Though
>> they are all lovely people, not all of
> On Aug 27, 2021, at 5:07 PM, Rowan Tommins wrote:
>
> On 27/08/2021 20:47, Olle Härstedt wrote:
>> As a followup for my previous post, I think this could be a good place
>> to start to enable attribute writers to create encapsulation mechanics
>> for composition, like namespace visibility,
On 27/08/2021 20:47, Olle Härstedt wrote:
As a followup for my previous post, I think this could be a good place
to start to enable attribute writers to create encapsulation mechanics
for composition, like namespace visibility, "internal" access or
friend classes.
In my experience PHP
Hi everyone,
I'm happy to announce that the vote for nullable intersection types is now
> open:
> https://wiki.php.net/rfc/nullable_intersection_types
>
> It'll close in two weeks, on the 27th.
>
The vote is now closed with a total of 38 votes: 26 against and 12 in favor.
The RFC is declined.
Hi,
As a followup for my previous post, I think this could be a good place
to start to enable attribute writers to create encapsulation mechanics
for composition, like namespace visibility, "internal" access or
friend classes.
There's an outline to an idea by Nikic here:
Hey Dan.
I see that you read what I wrote and intrepid it in the worst possible way. I
will try to be more clear and more carefully chose my words in the future.
I called it an “obvious mistake” because it was clear to me that we missed
something. We are not bad people or worse developers
Tobias wrote:
> I know you are not a bad person...
>
> The fact that you unprompted (as far as I can tell) decided to in
> detail specify how RMs should make their decision about an RFC is
> giving me a strong signal that you don’t trust the role of the Release
> Manager. The timing of your RFC
On Tue, 24 Aug 2021 at 20:02, Pierre Joye wrote:
>
> good evening Dan,
>
> First of all, could you please not merge many different mails in one single
> reply? Thanks.
No. This is a mailing list, where conversations get spread over
different forks of threads.
When a reply is relevant to
Nikita Popov wrote on 8/27/21 10:40:
>> If we don't want downstream users to redeclare the properties, why are
>> they protected?
>>
>
> To allow downstreams users to write $this->line = 123.
>
Got it. When I asked the question, I was thinking about passing it
through the constructor,
On Fri, Aug 27, 2021 at 5:35 PM Ben Ramsey wrote:
> Nikita Popov wrote on 8/26/21 14:57:
> > On Thu, Aug 26, 2021 at 8:34 PM Ben Ramsey wrote:
> >
> >> Nikita Popov wrote on 8/26/21 09:57:
> >>> Right. I at least do not plan to address this issue. If you take a
> >>> protected property and
Nikita Popov wrote on 8/26/21 14:57:
> On Thu, Aug 26, 2021 at 8:34 PM Ben Ramsey wrote:
>
>> Nikita Popov wrote on 8/26/21 09:57:
>>> Right. I at least do not plan to address this issue. If you take a
>>> protected property and publicly re-export it, then any compatibility
>> issues
>>> are on
On Tue, Aug 10, 2021 at 12:55 PM Philip Hofstetter <
phofstet...@sensational.ch> wrote:
> Hello
>
> The following valid <= PHP 8.0 code that intends to make the $line property
> public is a fatal error in 8.1
>
> class FooException extends Exception {
> public $line;
> }
>
> However, the
13 matches
Mail list logo
