You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The acronym problem description says to count dash as separator and ignore punctuation.
Then the tests start doing random other requirements like CamelCase.
Another example is the collatz tests throwing negative numbers at the function.
Is it policy that the descriptions not be enough to solve the challenges?
I really don't think this is unique to the Haskell track either.
The text was updated successfully, but these errors were encountered:
At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.
This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!
If you're interested in learning more about this auto-responder, please read this blog post.
The acronym problem description says to count dash as separator and ignore punctuation.
Then the tests start doing random other requirements like CamelCase.
Another example is the collatz tests throwing negative numbers at the function.
Is it policy that the descriptions not be enough to solve the challenges?
I really don't think this is unique to the Haskell track either.
The text was updated successfully, but these errors were encountered: