haskell VS problem-specifications

I am working the Exercism Haskell Track and one of the questions asks for a custom set implementation. I studied some community solutions to see what other folks are doing, and came across something that I don't quite understand.

Starting today, I'll resume solving exercises in Exercism, focusing on my Python and Haskell tracks.

I did see https://exercism.org/tracks/haskell , as well, but I'm not sure if that's what I'm looking for and I won't know until I make an account. I'd rather not make an account unless it actually provides what I'm looking for.

"Best" solution here: https://github.com/exercism/haskell/blob/main/exercises/practice/acronym/.meta/examples/success-text/src/Acronym.hs

Haskell is a really interesting language, and if you're comfortable with Scheme from 61a then many of the concepts carry over. However, Haskell has a pretty steep learning curve (in comparison to Clojure which is much closer to Scheme). I've been using https://exercism.org/tracks/haskell and been finding it fun so far.

To explore this space I created an Exercism exercise called dnd-character.

Exercises come from the problem specification repository.

That's going to take some time. Exercism have a standard set with a description and unit tests. The reason I got straight into the test type was because of need to conform to the unit tests.

To the wider Seed7 community: Would it be an impossible thing for any of you to contribute code to the Seed7 track on Exercism? Have a look at the full list of exercises on Exercism's github. Either paste your contributions in here, or send to bruceax at gmail dot com. Contributors will be formally acknowledged as per the Exercism docs (see the blurb about "File: .meta/config.json"). A minimum of 20 exercises is required to launch a track. There are other requirements.

Compare this with Exercism's problem specification, and try to figure out where additional exercises (if any) would fit into the Javascript syllabus.

There are a variety of predefined exercisies in Exercism that have yet to be implemented in Raku: https://github.com/exercism/problem-specifications/tree/main/exercises

First @AnAccountForReportingBugs suggested testing the mean/std.dev. via sampling, but that didn't persuade the crowd (myself included). There were two concerns: performance, and probability of false negatives. -- "Our unit tests should be 'too fast to notice'" -- "With which frequency will this test randomly fail?" -- "[...] I'd be happy to be proved wrong by a 100% reliable test that executes in <100ms." after which they rightfully responded,