>
> On 26 Jun 2025, at 18:07, Rowan Tommins [IMSoP] wrote:
>
> On 26/06/2025 17:53, Larry Garfield wrote:
>
>> Now here's the big one: Using enums rather than a bunch of constants is a
>> good change. However, I feel like it doesn't go far enough.
>
>
> 100% this.
>
> Writing "$ch->setO
Marco Deleu
> On 18 Apr 2025, at 14:54, Niels Dossche wrote:
>
> Hi
>
> Since this is a policy change, doesn't this need an RFC as well?
>
> Kind regards
> Niels
One can argue that this isn’t a policy change but rather just tooling to help
enforce a policy already in place:
https://www.p
> On 15 Nov 2024, at 20:42, Rob Landers wrote:
>
>
>> On Sat, Nov 16, 2024, at 00:34, Juris Evertovskis wrote:
>> Hey all,
>>
>>
>>
>> If you try to implement an interface that does not exist, you get the
>> ‘Interface “%s” not found’ error. Usually that’s useful as it points to a
>> cod
> On 24 Oct 2024, at 03:27, Larry Garfield wrote:
>
> Bundling Composer with PHP is an entirely different question with a host of
> additional concerns to consider, like whether the Composer maintainers would
> even want that. Let's please stay focused on the topic at hand.
>
> --Larry Garf
> On 11 Aug 2024, at 13:59, Christoph M. Becker wrote:
>
> On a general note, the whole administrative part of the RFC process
> feels like we're stuck in the 20th century. For instance, to start the
> vote, you are supposed to:
>
> * update the RFC page to "voting" status
> * add the doodle
> On 20 Jul 2024, at 11:30, Tim Düsterhus wrote:
>
> Hi
>
>> On 7/19/24 00:51, Christoph M. Becker wrote:
>> And frankly, how much code would be affected? I mean, does anybody
>> actually put a comment between `yield` and `from`? Is there a case
>> where this may make sense? "Because we ca
wi be done and it must be supported. If a
Ubuntu LTS user gets an error, pointing out that they're relying on an
accidental behavior only present in 9 patch releases of the entire PHP
lifecycle seems good enough.
> On 18 Jul 2024, at 16:05, Tim Düsterhus wrote:
>
> Hi
>
>
> On 17 Jul 2024, at 20:16, Juliette Reinders Folmer
> wrote:
>
> Hi all,
>
> I recently discovered a change was made to the Tokenizer in PHP 8.3.0 which
> now allows for a comment to exist between the `yield` and `from` keyword from
> the `yield from` keyword.
> Before PHP 8.3, this was a
Marco Deleu
>
>> You may have core developers that voted no due to maintenance burden, but if
>> said maintainer is no longer active and new maintainers don't mind it, it's
>> a moot argument because people changed.
>
> The maintenance burden argument is actually a good example of *not* bei
> On 15 Jun 2024, at 14:11, Rowan Tommins [IMSoP] wrote:
>
> I fundamentally disagree with this assertion.
>
> If somebody makes a valid point, it doesn't automatically become invalid
> because time has passed, or because nobody happens to repeat it in a later
> e-mail thread.
>
> If I cop
Marco Deleu
> On 19 Mar 2024, at 14:51, Ilija Tovilo wrote:
>
> Hi Robert
>
>> On Tue, Mar 19, 2024 at 5:24 PM Robert Landers
>> wrote:
>>
>> I've been thinking about this as an RFC for awhile, but with generics
>> being far off (if at all), I'd like to propose a useful idea: reusing
>>
Marco Deleu
> On 6 Oct 2023, at 19:39, Ben Ramsey wrote:
>
> On 10/6/23 11:18, Jakub Zelenka wrote:
>> Hi,
>>> On Fri, Oct 6, 2023 at 2:44 PM Ilija Tovilo wrote:
>>> https://wiki.php.net/rfc/rfc1867-non-post
>>>
>>>
>> It should probably explicitly mention that it uses the same inis like
12 matches
Mail list logo
