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
Hi all,
while going through the cpp track I noticed that a few exercises README.md provide incomplete instructions.
The exercises can frequently be completed inspecting the corresponding *_test.cpp, e.g. looking for the specific function name that the user is required to define. E.g., these are the ones I have found out of the 15 I have gone through so far.
Hello. Thanks for opening an issue on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed.
That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there.
Note: If this issue has been pre-approved, please link back to this issue on the forum thread and a maintainer or staff member will reopen it.
welcome to Exercism. I am happy to hear that you enjoy the C++ track and want to improve it.
Your ideas have been discussed several times on the forum. This post is the most recent example. I think the explanation of the current procedure by Siebenschläfer is pretty interesting.
Hi all,
while going through the cpp track I noticed that a few exercises
README.md
provide incomplete instructions.The exercises can frequently be completed inspecting the corresponding
*_test.cpp
, e.g. looking for the specific function name that the user is required to define. E.g., these are the ones I have found out of the 15 I have gone through so far.I would like to use the opportunity of going through the exercises to spot and amend those affected.
Would you be interested in a PR on this?
The text was updated successfully, but these errors were encountered: