I ended up implementing my own version of a generator template class as an experiment with C++20 coroutines, and then somebody over at codereview.stackexchange.com gave me a link to this project.
It looks like a lot of my implementation is pretty similar to what I saw here. One thing I did differently, though, was to create a class unique_coroutine_handle - heavily inspired by unique_ptr - to abstract out what in the code here is a manual call in the generator destructor.
I found that this made the code probably a bit more readable and maintainable - I no longer needed any custom destructor, move constructor, or move assignment in the generator class; and the compiler was able to deduce on its own that the generator class cannot be copy constructible or copy assignable.
I thought it might also be useful in other classes here. For instance, in the event handlers registered with a scheduler for awaitables such as async_read_operation you might create a capture of a unique_coroutine_handle (and then the lambda destructor would automatically handle cleaning up the coroutine state if the scheduler is stopped early); and the event handler body could include something like handle.release().resume(); . Though these musings come with the caveat that I haven't actually tried implementing anything similar to this part of the library yet.
I ended up implementing my own version of a
generatortemplate class as an experiment with C++20 coroutines, and then somebody over at codereview.stackexchange.com gave me a link to this project.It looks like a lot of my implementation is pretty similar to what I saw here. One thing I did differently, though, was to create a class
unique_coroutine_handle- heavily inspired byunique_ptr- to abstract out what in the code here is a manual call in thegeneratordestructor.I found that this made the code probably a bit more readable and maintainable - I no longer needed any custom destructor, move constructor, or move assignment in the
generatorclass; and the compiler was able to deduce on its own that thegeneratorclass cannot be copy constructible or copy assignable.I thought it might also be useful in other classes here. For instance, in the event handlers registered with a scheduler for awaitables such as
async_read_operationyou might create a capture of aunique_coroutine_handle(and then the lambda destructor would automatically handle cleaning up the coroutine state if the scheduler is stopped early); and the event handler body could include something likehandle.release().resume();. Though these musings come with the caveat that I haven't actually tried implementing anything similar to this part of the library yet.