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
Based on something that I brought up on the Racket track a while back, I think the hello-world objective "Modify the provided code so that it produces the string "Hello, World!" is potentially misleading -- the code isn't itself producing "Hello, World!" when it's run, it's the test runner that's checking the return value.
I suggested changing Racket's description to "so that the function returns the string" instead, but the track maintainer suggested I bump it up a tier and bring it up here instead, to see if there's some language or clarification that'd be potentially better for all tracks.
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.
Based on something that I brought up on the Racket track a while back, I think the hello-world objective "Modify the provided code so that it produces the string "Hello, World!" is potentially misleading -- the code isn't itself producing "Hello, World!" when it's run, it's the test runner that's checking the return value.
I suggested changing Racket's description to "so that the function returns the string" instead, but the track maintainer suggested I bump it up a tier and bring it up here instead, to see if there's some language or clarification that'd be potentially better for all tracks.
The text was updated successfully, but these errors were encountered: