Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NOT-AN-ISSUE] co_resource is excellent #2

Open
david-bakin opened this issue Jan 7, 2022 · 0 comments
Open

[NOT-AN-ISSUE] co_resource is excellent #2

david-bakin opened this issue Jan 7, 2022 · 0 comments

Comments

@david-bakin
Copy link

[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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant