Re: [PATCH 06/18] chainlint.pl: validate test scripts in parallel

From: Eric Wong <e@80x24.org>
Date: Sep 6, 2022, 22:35 UTC
Message-ID: <20220906223537.M956576@dcvr>
In-Reply-To: <62fc652eb47a4df83d88a197e376f28dbbab3b52.1661992197.git.gitgitgadget@gmail.com>

Eric Sunshine via GitGitGadget <gitgitgadget@gmail.com> wrote:

> +unless ($Config{useithreads} && eval {
> +	require threads; threads->import();

Fwiw, the threads(3perl) manpage has this since 2014:

       The use of interpreter-based threads in perl is officially discouraged.

I was bummed, too :< but I've decided it wasn't worth the effort to deal with the problems threads could cause down the line in future Perl versions. For example, common libraries like File::Temp will chdir behind-the-scenes which is thread-unsafe.

(of course I only care about *BSD and Linux on MMU hardware, so I use SOCK_SEQPACKET and fork() freely :>)

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.