I just learned today from a post on the Exercism discord server: if I’m using the exercism CLI to submit a solution, I can mark an exercise complete after submitting the solution, despite that my solution fails to pass its tests on the server. Sorry, I wasn’t aware. (I thought I had to pass the unit tests sever-side before I could declare an exercise complete.) Was there some fine-print I failed to read when I got started with Exercism?
No worries though - I studied a lot of tutorials and references over the last several weeks about various ways to make pwsh run functions concurrently. Although none of my submission attempts passed the server’s tests, they each passed 100% on my own workstation (8 CPU cores) with Invoke-Pester runtimes ranging from 45 seconds all the way down to 2.2 seconds. It turns out there’s a rich variety of concurrency-capable tools in pwsh, ranging from cmdlets such as ForEach-Object or Start-Job or Start-ThreadJob, to .NET classes including but not limited to [runspacefactory] or [System.Linq.ParallelEnumerable]. It was fun to explore some of these as I tried (unsuccessfully it turns out) to pass tests server-side.
I hope the comment I left in the code is appropriate – a genAI helped me tone down my snark. 