Nitpicks While Working Through Exercises

Hello! I’m working through the Haskell track. I’d like to say I’m grateful for such a lovely set of exercises!

As I work through them, I thought I’d note any nitpicks I come across, in case a proofreading pass is helpful. I am happy to promote any of these to pull requests. I am also perfectly happy to be ignored. ;) Just thought I’d write down what I ran across in an attempt to contribute.

So far:

“Darts” – The problem statement doesn’t specify what should happen if a dart lands exactly on a ring. You can figure it out by looking at the test cases, but it seems like the problem statement should probably say.

“RNA Transcription” – The problem statement asks for an invalid input to return the first invalid character. However, the set of tests doesn’t cover that case. The only applicable test inputs the string “ACGTXXXCTTAA” and expects back “Left X”. This could be the last X, not the first one. ;) Nit picky, but it seems like the tests should cover the specification, especially because approaching a list from the left or the right is the sort of thing a language noob like me is prone to mess up.

1 Like

Exercism explicitly takes a Test Driven Development approach and expects students to determine requirements from failed tests. The descriptions do not cover every aspect of the requirements and do not intend to do so.

2 Likes

Oh, okay! Thanks for letting me know. :)

2 Likes