Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127697
Precedence: bulk
MIME-Version: 1.0
References: <bc1ec15125844c78a6aa23dce6148af9@danielkesselberg.de>
 <8b76a3d4-4583-4849-a75f-00f645191247@gmail.com> <db784868-187d-42ff-9575-64b5ca70f50b@app.fastmail.com>
 <57f7ed3e-6bef-434d-83db-fd729ff43fc9@gmail.com> <20250527163747.ADA6D1A00BD@lists.php.net>
 <0FC66A63-1284-41AF-AA27-27F657EB57AF@php.net> <20250527171352.552DD1A00BD@lists.php.net>
 <adc31192d44d2d0ea12624fcb80f4ae4@danielkesselberg.de>
In-Reply-To: <adc31192d44d2d0ea12624fcb80f4ae4@danielkesselberg.de>
Reply-To: erictnorris@gmail.com
Date: Tue, 17 Jun 2025 12:37:35 -0400
Message-ID: <CA+NMNO1XAyYpYs+EoTT4PCR0GmOsx-NUdtUpWO+Zt+RpqLEwgg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Add num_available_processors
To: Daniel Kesselberg <mail@danielkesselberg.de>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: eric.t.norris@gmail.com (Eric Norris)

Hello!

On Sun, Jun 15, 2025 at 1:33=E2=80=AFPM Daniel Kesselberg
<mail@danielkesselberg.de> wrote:
>
> Hi,
>
> Thanks for all your feedback on the RFC.
>
> I've updated the RFC to incorporate most of your feedback:
> https://wiki.php.net/rfc/num_available_processors
>
> 1) The limitation, that the CPU affinity mask is ignored
> 2) The naming discussion

I'm curious, is there a reason why you feel that introducing a new
namespace should be under "Future Scope", instead of a part of this
RFC? I expect there would be some bikeshedding over the namespace
name, but there is / will be some bikeshedding around a non-namespaced
name in the first place, so it feels like a good opportunity to
embrace namespaces in the standard library.

I ask this because I've been very slightly interested in introducing a
Curl namespace since the "Throwable Hierarchy Policy for Extensions"
(https://wiki.php.net/rfc/extension_exceptions) RFC and my own
personal "Persistent curl share handle"
(https://wiki.php.net/rfc/curl_share_persistence_improvement) RFC.

> How do we continue? ;) I see there are various ideas how to approach it,
> is that something you would vote (let's do a or b) on, or how does that
> work?

Relating to my above question, if you're open to it, I would be happy
to work with you on your RFC to (a) figure out a good namespace name
and (b) update the RFC to match.