Currently we have some exercises with hints as comments in the test suite and/or in the stub solution.
Hints in the stub solutions are convenient - users are almost forced to read them - but proved to be a mess, because most users submit the code with the comments.
Hints in the test suite are not that bad, but they force the users to inspect it. I think that, ideally, users should get feedback running the tests, not studying them.
Anyway, considering that the contents of HINTS.md is automatically included in the README.md, it is the perfect place for hints. We just need to make it happen!
All the exercises that already have a HINTS.md file share the same formatting,
so we are using this as a standard for now.
This issue will track the migration's progress as soon as we have a complete list of exercises to be changed.
Tracking changes
Currently we have some exercises with hints as comments in the test suite and/or in the stub solution.
Hints in the stub solutions are convenient - users are almost forced to read them - but proved to be a mess, because most users submit the code with the comments.
Hints in the test suite are not that bad, but they force the users to inspect it. I think that, ideally, users should get feedback running the tests, not studying them.
Anyway, considering that the contents of
HINTS.mdis automatically included in theREADME.md, it is the perfect place for hints. We just need to make it happen!All the exercises that already have a
HINTS.mdfile share the same formatting,## Hintsso we are using this as a standard for now.
This issue will track the migration's progress as soon as we have a complete list of exercises to be changed.Tracking changes
hspec)pov (nothing to fix)hspec)hspec)