hsf-training / hsf-training/cpluspluscourse
STL vs. standard library
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 313
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
I would like to add some more standard library components to the overview on this slide:

Specifically: threads mutexes, atomics, regular expressions, filesystem access, random number engines and distributions, date and time utilities, ...
Not because I want to explain all this, but I want students to have a rough sketch on what they have at their disposal.
But that now conflicts with the chapter title, which is "STL". However, the Standard Template Library is not technically the same as the C++ Standard Library. STL was the name of a library from Alexander Stepanov et. al. proposed for standardization in C++98 and became part of the C++ Standard Library. I know many people still call that part of the C++ Standard Library STL, but it is technically not correct. And it is even less correct, if I would start mentioning more standard libraries like the list above in the chapter STL.
What should we do about this? Rename the chapter STL to standard library? Leave it? Add a new slide giving an overview of the standard library and claiming the STL is one part of the standard library?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the slide shown in the issue and the chapter currently titled "STL". Decide whether the overview should be renamed to "standard library," expanded with the listed components, or split into a separate overview slide. Done means the terminology and slide structure clearly distinguish STL from the broader C++ Standard Library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100