Make performance and clarity updates for C++17
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 107
- Forks
- 26
- Avg merge
- 8d 11h
- Merged PRs (30d)
- 2
Description
@kab163 did the great work to get everything behaving and requiring C++17 for all compilers in #171. There are a number of workarounds in camp to support C++14 compilers, and in some cases even 11, and we currently don't document the required version. This is partially just documentation, but should also include using things like actual fold expressions to implement the appropriate folds to save compile times.
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 changes in #171 and locate the C++14 and C++11 workarounds used for folds. Identify where the required compiler version should be documented and which folds can use C++17 expressions; done means the requirement is documented and the relevant workarounds are replaced without regressing compilation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100