isocpp / isocpp/CppCoreGuidelines
Should function parameter passing guidance cover async functions
Open
@ChrisGuzak is already working on this.
Since Mar 11, 2021.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
When passing values to functions that use co-routines those functions need to ensure they don't access values by reference in the continuation. This means parameter choice pushes you do taking things by value, for example a RECT class (4 numbers) is often best passed by const& but if it needs to be used after the suspension point by value is better.
Should this be discussed in F.16?
Contributor guide
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.
Assessment
This issue has not been assessed yet.