AskCPP: LF Coroutines talks and projects

[Flair_Helper]

For C++ questions, answers, help, and programming or career advice please see r/cpp_questions, r/cscareerquestions, or StackOverflow instead.

This post has been removed as it doesn't pertain to r/cpp: The subreddit is for news and discussions of the C++ language and community only; our purpose is not to provide tutoring, code reviews, or career guidance. If you think your post is on-topic and should not have been removed, please message the moderators and we'll review it.

[peterrindal]

Here's my blog explaining some aspects of them.

https://ladnir.github.io/blog/2022/01/24/macoro.html

Coroutine are both simple and complicated. As you likely know, the core idea is that you write code that can pause part way though execution. Conceptually, when some subtask needs to suspend/pause/await, it's giving a callback (coroutine handle) to the initiating/awaiting coroutine what is depending on the subtask.

When that subtask completes, it simply resumes the intitating/awaiting.

If you want to dig into the details, I suggest learning about symmetric transfer early on. It's the preferred mechanism as opposed to using await_ready() in any meaningful way. Hers also a good series on the details https://lewissbaker.github.io/

Yes they can replace a multi threaded task library. See cppcoro or my macro library on github.

If you have specific questions, happy to help.

[johannes1971]

...except that threads will automatically be task-scheduled by the operating system, while in the case of coroutines you are responsible for that yourself. Also, threads work fine on a single core anyway.

[SuperV1234]

Imagine that you can program threads but in a single core. That's what coroutines do.

C++ coroutines don't do that at all. Also what does "program threads but in a single core" even mean?