Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125828
Content-Type: multipart/alternative;
 boundary="------------TiteiDGU9DNFB4Jn9Zr0DC4G"
Message-ID: <4bf70932-d465-4359-9510-62d457d6e218@scriptfusion.com>
Date: Mon, 21 Oct 2024 21:50:49 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Change behaviour of array sort functions to
 return a copy of the sorted array
To: internals@lists.php.net
References: <ZydAaayECTRNG8Ackhb0tDgYjmdFKnkW4p0ISWlLFP5My4CsJBR1KKTylrD14Ags2GUyBLoJPf68N6Z6LoVzjG-tru8YAbmi74W5xzSkJ8I=@gpb.moe>
 <y61nFg8JnfpzCsL25kyI35RiCtTm7MHW_Zn3TY81lKHkmdagnyTMk0f73FQV-xuu1aRl4401vOtG5ZbK5j5Xx4_UCkF1TJnoGNm2Aw4GlSw=@gpb.moe>
 <CAPyj-LDbEYXYDROO5_M1WZWUw1pCWhhVREEvqgQuHGXTBLpaHw@mail.gmail.com>
 <HRchGMNN6j5OCtAss04zESt4UVSCxl5qka3EFDnARx-_0cqXsF7W7IOOI6OXZiuG0e-FLpALPeHGTV0qWw9WbHApmrGdN5y9OBmgpzwTCmw=@gpb.moe>
 <CAPyeZ4NnoJU0FKFGPOg+KFYmQgabCCuG8Owh6V-5DTCDEru8QA@mail.gmail.com>
 <CAKVXxD9xC8OuKAoLcUu_-Bic9XjhP9_Y63wzj-+PtX-NUwn0Lw@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CAKVXxD9xC8OuKAoLcUu_-Bic9XjhP9_Y63wzj-+PtX-NUwn0Lw@mail.gmail.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------TiteiDGU9DNFB4Jn9Zr0DC4G
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 21/10/2024 21:41, mickmackusa wrote:
> On Tue, 22 Oct 2024, 02:30 Valentin Udaltsov, 
> <udaltsov.valentin@gmail.com> wrote:
>
>
>     What if instead of this proposal we reimplement all of the array
>     functions in a different namespace and fix a lot of other problems and
>     inconsistencies?
>
>     Array\map(iterable $iterable, callable $mapper): array
>     Array\sort(iterable $iterable, int $flags = SORT_REGULAR): array
>     ...
>
>     -- 
>     Valentin
>
>
> Getting off-topic here
The whole discussion thread is "off-topic" in the context of the RFC, 
but I don't consider that a problem; it's a useful discussion to have 
whether the RFC sparked it or not.

Regarding the Array\map(iterable $iterable, ...) signature, if new 
functions are to accept iterables instead of arrays (as they absolutely 
should) then the `Array` namespace makes no sense. But at that point 
we're basically just putting https://github.com/nikic/iter in core (not 
that that's a bad thing).

Cheers,
Bilge

--------------TiteiDGU9DNFB4Jn9Zr0DC4G
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 21/10/2024 21:41, mickmackusa wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKVXxD9xC8OuKAoLcUu_-Bic9XjhP9_Y63wzj-+PtX-NUwn0Lw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">
        <div>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Tue, 22 Oct 2024, 02:30
              Valentin Udaltsov, &lt;<a
                href="mailto:udaltsov.valentin@gmail.com"
                moz-do-not-send="true" class="moz-txt-link-freetext">udaltsov.valentin@gmail.com</a>&gt;
              wrote:<br>
            </div>
            <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
              What if instead of this proposal we reimplement all of the
              array<br>
              functions in a different namespace and fix a lot of other
              problems and<br>
              inconsistencies?<br>
              <br>
              Array\map(iterable $iterable, callable $mapper): array<br>
              Array\sort(iterable $iterable, int $flags = SORT_REGULAR):
              array<br>
              ...<br>
              <br>
              -- <br>
              Valentin</blockquote>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Getting off-topic here</div>
      </div>
    </blockquote>
    The whole discussion thread is "off-topic" in the context of the
    RFC, but I don't consider that a problem; it's a useful discussion
    to have whether the RFC sparked it or not.<br>
    <p>Regarding the Array\map(iterable $iterable, ...) signature, if
      new functions are to accept iterables instead of arrays (as they
      absolutely should) then the `Array` namespace makes no sense. But
      at that point we're basically just putting
      <a class="moz-txt-link-freetext" href="https://github.com/nikic/iter">https://github.com/nikic/iter</a> in core (not that that's a bad
      thing).</p>
    <p>Cheers,<br>
      Bilge<br>
    </p>
  </body>
</html>

--------------TiteiDGU9DNFB4Jn9Zr0DC4G--