You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[I couldn't find any contact information for you except Twitter, and I don't do Twitter. Feel free to DELETE this non-ISSUE if you don't want it cluttering things up.] [Maybe consider enabling "Discussions" here? Though I have no idea what kind of ongoing work that would commit you to.]
I consider co_resource an excellent tool, and, perhaps more, an excellent example of the way coroutines - and threads too - should be used in C++. That is, as built-in to the language (or library) both coroutines and threads are extremely low-level and are not (IMO) to be used directly. They need to be wrapped in higher level semantic constructs for ease of use, ease of understanding, and correctness of use. That is, any of the tricky details of using these low level constructs correctly and safely should be considered and handled by a wrapper that presents a clean, usable interface of some particular use case ("pattern" to some people) to the programmer.
And these wrappers do not need to be large all-encompassing frameworks either. In fact, I myself would prefer them to not be such frameworks. Just simple small tools you can use with your existing way of doing things, easily.
co_resource is an excellent first tool for my coroutine-wrapper toolbox.
The text was updated successfully, but these errors were encountered:
[I couldn't find any contact information for you except Twitter, and I don't do Twitter. Feel free to DELETE this non-ISSUE if you don't want it cluttering things up.] [Maybe consider enabling "Discussions" here? Though I have no idea what kind of ongoing work that would commit you to.]
I consider
co_resource
an excellent tool, and, perhaps more, an excellent example of the way coroutines - and threads too - should be used in C++. That is, as built-in to the language (or library) both coroutines and threads are extremely low-level and are not (IMO) to be used directly. They need to be wrapped in higher level semantic constructs for ease of use, ease of understanding, and correctness of use. That is, any of the tricky details of using these low level constructs correctly and safely should be considered and handled by a wrapper that presents a clean, usable interface of some particular use case ("pattern" to some people) to the programmer.And these wrappers do not need to be large all-encompassing frameworks either. In fact, I myself would prefer them to not be such frameworks. Just simple small tools you can use with your existing way of doing things, easily.
co_resource
is an excellent first tool for my coroutine-wrapper toolbox.The text was updated successfully, but these errors were encountered: