On 20/07/2025 02:58, Nick wrote:
>
> Hey Niels,
>
Hey Nick
>
> In before: I personally didn’t have a problem with Tim joining in late.
>
>
> I, however, want to express that I don’t feel anything productive happens at
> this point.
>
>
> My personal impression is, there wasn’t anything n
On 18/07/2025 16:15, Claude Pache wrote:
> Hi,
>
Hi Claude
> 1. The RFC says: “CHIPS technology was introduced not so long ago, but still
> has “little” adoption (currently “only” available in Blink-based browsers).”
>
> It might be useful to add the following precisions, so that we are more
Recently introduced pipeline operator is great, but together with
assignment operator it will lead to mixing top-to-bottom and
bottom-to-top code reading directions and vertigo.
To reduce this problem i'd like to discuss the idea of left to right
assignment operator. The draft rfc can be found
Hi Vadim
The example where |> is used to assign to a variable seems not possible to me.
It will lead to an ambiguity when $result is a callable for example.
Therefore, |>= is the only possibility of the two your proposed.
Kind regards
Niels
Hi Vadim
Thanks for your follow-up.
On Sun, Jul 20, 2025 at 11:54 AM Vadim Dvorovenko
wrote:
>
> Recently introduced pipeline operator is great, but together with
> assignment operator it will lead to mixing top-to-bottom and
> bottom-to-top code reading directions and vertigo.
>
> To reduce thi
> On 20. Jul 2025, at 15:54, Niels Dossche wrote:
>
> On 20/07/2025 02:58, Nick wrote:
>>
>> Hey Niels,
>>
>
> Hey Nick
Hey Nils,
>> The whole controversy is about `get`.
>>
>
> That's true.
> Note though that the fact that the RFC still includes this does show a
> non-consensus from t
Hi Rob,
I'm going to respond to a few points from earlier emails here instead
of each one.
On Sat, Jul 19, 2025 at 6:13 AM Rob Landers wrote:
>
>
>
> On Sat, Jul 19, 2025, at 12:09, Claude Pache wrote:
>
>
>
> Le 19 juil. 2025 à 09:46, Rob Landers a écrit :
>
>
>
> On Sat, Jul 19, 2025, at 03:0
Sorry, that's my first reply to mailing list discussion, maybe i'm not
doing it right.
Ilija wrote:
The problem you're describing is not unique to pipes. Code like this
is quite common. $x = foo() ->bar() ->baz(); If we decide this is a
problem (which I fundamentally disagree with), then we s
Hello, my two cents,
On Thu, Jun 19, 2025 at 9:09 PM Marc Bennewitz wrote:
> Hi,
>
> During the discussion about the year 2038 issue it turned out that maybe
> it's time to drop support for 32-bit of PHP completely.
>
> Based on that I have created an RFC to deprecate 32-bit build in 8.next
> an
On Sun, Jul 20, 2025, at 3:54 AM, Niels Dossche wrote:
>> When is a discussion allowed to be considered wound down?
> This has never been defined and always has a subjective part.
> In general, no one will block you from bringing it to a vote if no
> substantial changes have been made to the RF
I have opened the vote for property hooks on readonly properties. The vote
will run for two weeks, until 3 August.
As noted, there are two independent votes, one for allowing a "get" hook on
readonly properties, and one for allowing a "set" hook on readonly properties.
Either one can pass or
On Sun, Jul 20, 2025, at 5:22 AM, Ilija Tovilo wrote:
> Hi Vadim
>
> Thanks for your follow-up.
>
> On Sun, Jul 20, 2025 at 11:54 AM Vadim Dvorovenko
> wrote:
>>
>> Recently introduced pipeline operator is great, but together with
>> assignment operator it will lead to mixing top-to-bottom and
>>
On Sun, Jul 20, 2025, at 19:18, Eric Norris wrote:
> Hi Rob,
>
> I'm going to respond to a few points from earlier emails here instead
> of each one.
>
> On Sat, Jul 19, 2025 at 6:13 AM Rob Landers wrote:
> >
> >
> >
> > On Sat, Jul 19, 2025, at 12:09, Claude Pache wrote:
> >
> >
> >
> > Le 19
13 matches
Mail list logo
