Overview
The course examples are all written in .hpp files. However, many students based on their introductions to C++ think that this is optional and that they can split their file in to .hpp/.cpp file pairs.
Discussion
This split header-file pattern breaks down quickly when attempting to leverage the advanced features of C++. Although I don't know the reasons myself, other than frustrating experience, it would be good to discuss the differences between the different file types.
This kind of introduction seems like an appropriate kind of bridge to connect what students already know with what they need to know for this specific context in HPC.
Content Location
Ideally, this new section would be linked to from the Lesson 1 reading page.
It probably makes sense to include the content in the Typical Knowledge Gaps resource.
Therefore, it could make sense to add content to the section, and then provide a quick link to it from the Lesson 1 page.
Overview
The course examples are all written in
.hppfiles. However, many students based on their introductions to C++ think that this is optional and that they can split their file in to.hpp/.cppfile pairs.Discussion
This split header-file pattern breaks down quickly when attempting to leverage the advanced features of C++. Although I don't know the reasons myself, other than frustrating experience, it would be good to discuss the differences between the different file types.
This kind of introduction seems like an appropriate kind of bridge to connect what students already know with what they need to know for this specific context in HPC.
Content Location
Ideally, this new section would be linked to from the Lesson 1 reading page.
It probably makes sense to include the content in the Typical Knowledge Gaps resource.
Therefore, it could make sense to add content to the section, and then provide a quick link to it from the Lesson 1 page.