Newsgroups: perl.perl5.porters
Path: csiph.com!fu-berlin.de!bofh.it!nntp.perl.org
Xref: csiph.com perl.perl5.porters:99844
Mailing-List: contact perl5-porters-help@perl.org; run by ezmlm
Received-SPF: pass (dmarc-service-6ccc8c884f-7lc4z: domain of bruhat.net designates 185.26.105.233 as permitted sender) client-ip=185.26.105.233; envelope-from=philippe@bruhat.net; helo=smtpm2.myservices.hosting;
Date: Thu, 5 Feb 2026 11:31:57 +0100
To: Marc Chantreux <mc@unistra.fr>
Cc: perl5-porters@perl.org
Subject: Re: Gain performances and fix some issues using XS
Message-ID: <aYRxnYw7w5VMp4DW@kapow.home>
References: <aYRsxwEr2Jop5mtY@prometheus>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aYRsxwEr2Jop5mtY@prometheus>
Approved: news@nntp.perl.org
From: philippe@bruhat.net ("Philippe Bruhat (BooK)")

On Thu, Feb 05, 2026 at 11:11:19AM +0100, Marc Chantreux wrote:
> 
> 1. make it faster at execution
> 2. make it even faster/easy to write with expressions instead blocks
>    with filter/apply (which are "on demand" conterparts of grep/map).
> 3. put a value back to the stream in case of failure

Point 2 reminds me of Graham's generic "iterators" proposal that we
discussed during the PTS in 2023 in Lyon. Generalizing the idea of map
and grep in the language.

Maybe it's time someone gets that PPC written?

-- 
 Philippe Bruhat (BooK)

 Only a fool follows orders without knowing why.
                                    (Moral from Groo The Wanderer #86 (Epic))