c: Inconsistency in headers provided
Most exercises provide at least the header to get you started (so you know what API you are implementing)… but some give you nothing. Example: circular_buffer… this makes it much harder to get started.
Is this somehow intentional? Could we agree on what amount of boilerplate exercises should start with and then would PRs be welcome here?
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 1
- Comments: 18 (18 by maintainers)
Looks like I picked the right week to be on vacation.
This may possibly help to solve #807 also?
That’s a reasonable compromise I think.
IIRC we previously completed an initiative to have stub headers for all exercises up to a certain point, with none after that point
I don’t recall up to which exercise exactly, but it was approximately 1/4 or 1/3 of the way through the track.
I’m guessing more have crept in since then though.
Having done 44 solutions myself and having mentored 200+ solutions, I can’t say I recall the lack of forward declarations for some exercises to have been much of a problem for myself or others. I may have had a very few students express they had difficulty, but I don’t remember any specifically. When lacking forward declarations, my own approach has been to look at the tests to see what function signature(s) they expect and take it from there. It may be a bit challenging to have to do that, but it’s also rewarding when, hey! I figured it out! 😄